[Opendnssec-develop] maintainers list

[Jerry Lundström]

Hey all,

On Mon, Mar 5, 2012 at 3:47 PM, Matthijs Mekking <matthijs at nlnetlabs.nl> wrote:
>
> * Create a tarball release candidate (including checksum)
> * Announce it to the maintainers list, with the request to test it
> * Give it a week or so to receive feedback.
> * If no showstoppers are reported, do the actual release. Otherwise,
> fix stuff and make a new release candidate.

I've been thinking about this some and would like to extend this
suggestion with a two week QA process.

I believe it would be relatively simple to setup a continues running
setup of OpenDNSSEC on all build platforms, this would be a separate
installation of OpenDNSSEC running signing on a few example zones.
Jenkins could then be used to poke at OpenDNSSEC with normal
operations like adding and deleting zones, resigning and key rollovers
(I would need help writing these test cases).

The process it would look something like this.
- if any step fails we start over
- if any changes are needed we start over, increase rc

* Can we release 1.3.7
* Tag 1.3.7rc1, tarball, upload to site
* Announce, link + checksum
* Switch continues running setup (CRS) to tag 1.3.7rc1
* Wait 2 weeks
* Copy tag 1.3.7rc1 to 1.3.7qa1 (or plain 1.3.7, but a QA tag might be nice)
* Announce, link + checksum

Thoughts?
/Jerry