[OpenAFS-devel] formalized release schedules, and release team, for feature releases (1.5.x, and future)

[Matt Benjamin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi List,

The openafs 1.5.56 could have been better in a couple of ways, and I'd
like to take th opportunity to bring up a couple of ideas that I think
at least worthy of discussion.

1. Formalize 1.5.x/feature release schedules

The 1.5.x CVS branch represents the current feature release for Unix
platforms.  I'd like to propose that this makes it important enough to
justify a bit more formal release management for 1.5.x releases.
Specifically, I think that there should be some advance notice published
to this list indicating the branch point from which the release is
planned to be made, and providing opportunity for the impending release
to be test built, and fixes to be suggested, where needed.  This is what
is already done for stable (1.4.x) releases, except that feature release
are distributed as source, and there is no need to collect builds.

2. I'd like to request formally that the gatekeepers make it possible
for willing volunteers like myself to join the release team, so that we
can help with this type of work.

3. Discussing this topic earlier in the morning, Derrick reminded me
that the 1.5.x branch is eventually intended to become a stable 1.6
branch--this has been discussed previously, for example, at the
OhioLinux hackathon in Oct.  There are open issues pending for the 1.6
feature baseline, that will need to be worked out and worked on before
that point.  I'd like to propose creation of a 1.6 release steering
committee, which would meet in conference.openafs.org on a weekly or
biweekly basis, and assist in the process.  Of course, I volunteer to
participate in such a committee.

Matt

- --

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJa9aGJiSUUSaRdSURCNo/AJ4/HGwy11nc839MPO05+thA0UR8tgCfbU2j
m3mwxlfiZ4P4OrgvauKT300=
=dur7
-----END PGP SIGNATURE-----