[Systers-dev] Questions about Release Management Process

[Jennifer Redman]

We have a few items in our release management process that need to be
improved and I'd love some suggestions/ideas how to approach.

- Release Notes -- what is the best way to handle release notes?  Should
this just be a "readme" file that is included with each release?

- Release Numbering - anyone have any preferences on release numbering?

- Patches for specific features - right now we pull the entire repo - which
includes all of our modifications to mailman to our dev/prod server.  This
makes it difficult for others to use the dlist functionality.  We originally
had some patches -- just for dlists -- but those need to be updated and
doc'd.  Anyone willing to be the dlist patch maintainer?  Essentially this
would make it easier for someone else to port to newer (or older versions)
of mailman and start working against MM 3 -- which has just had a new alpha
release.

- Commit access to the development branch and cli access to our test server.
 I'm of the opinion that the more people who know how to do things -- the
better.  The flipside is security, of course.  Anyone have any suggestions
on how to balance the two?

- Testing cycles -- how to get more people involved.  Any suggestions?

-  Release team -- I'd like to put together an actual release-team that
maybe rotates the release-manger job.  Anyone interested?

Thanks,
Jen