On Fri, 2018-05-18 at 09:30 +0200, Thorsten Kukuk wrote:
> Hi,
>
> On Thu, May 17, Dmitry V. Levin wrote:
>
> > On Thu, May 17, 2018 at 03:53:51PM +0200, Tomas Mraz wrote:
> > > Yes, we can keep the old releases on
linux-pam.org and do new
> > > ones on
> > > github.
> >
> > Fine with me.
> > I think we can also also make the tag and release tarballs signed.
>
> Who has experience with releasing and signing this on
github.com
> and can do that?
> Or can give me a step by step instruction?
>
> I would afterwards adjust
linux-pam.org.
As for releasing:
1. we need to adjust NEWS and configure.ac with the new version info
and commit and tag it with'Linux-PAM-1.3.1' tag.
2. Then you just create normal release tarball and upload it to https:/
/github.com/linux-pam/linux-pam/releases via the "Draft a new release".
3. For signing I think it has to be done manually with
gpg2 --sign -a -b <tarball>
Dmitry, is there anything else I forgot?
Just a few comments on signing:
Signed tags are usually made using "git tag -s".
Detached signatures of release tarballs are usually uploaded along with
these tarballs to the same location using the same "Draft a new release"
interface.
--
ldv