NTPsec release checklist

[Mark Atwood]

Hi!

I have added a draft of the release checklist to devel/hacking.txt

Please look it over, and give feedback.
My next rev of it will include the actually command line commands..

Thank you!

..m


> -----Original Message-----
> From: Eric S. Raymond [mailto:esr at thyrsus.com]
> Sent: Tuesday, September 27, 2016 2:02 PM
> To: Atwood, Mark <mark.atwood at hpe.com>
> Cc: Hal Murray <hmurray at megapathdsl.net>
> Subject: Re: Release checklist
>
> Hal Murray <hmurray at megapathdsl.net>:
> >
> > esr at thyrsus.com said:
> > > I think that's the right answer. I'll do the move to the website and
> > > start on a release checklist.
> >
> > I've been working on a checklist for a while.  I was hoping Mark would
> > send some details, but that hasn't happend.  Here is my list:
> >
> > Pre-Release:
> >   Check issues
> >   Send warning message
> >   wait N days
> >
> >   Run tests:
> >     Check parser
> >     Various configurations
> >
> > Release:
> >   bump VERSION: edit, commit, push
> >   Add tag, commit(?), push
> >   bump VERSION: edit, commit, push
> >
> >   make tarball
> >
> >   send release message
> >
> > - Send a PGP signed mail to the list when you make a release that
> >   includes the sha256sum
> > - You put that sha256sum also on the ftp dir
> > - You also sign the the released files with pgp
> >
> >
> > ------------
> >
> > Things like updating a list of known-good systems only make sense if
> > there is sufficient advanced warning.
>
> Mark, how close is this to what you do on release?  I think we should
> document our procedure, especially the cryptographic measures to ensure
> source integrity, well before 1.0. This is an assurance to potential users.
>
> The only item we can probably strike is build testing.  Jason Azze has
> buildbots doing that continuously.
> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20160928/e17f9c5c/attachment.html>