On 7/10/06, C. Michael Pilato <cmpilato@collab.net> wrote:
> I dunno about others, but I find it kind of hard to keep track of the status
> of any one of our releases as it going through the release process.
> Generally speaking, I have just as much information as the release manager's
> most recent status email. I propose that we use our issue tracker to track
> release status.
I think it's that the release process is too constipated. I'm not
sold that using Issuezilla is the solution here.
The release process should be:
1. Someone says "I'm going to roll a release on Friday." to dev@svn
2. People who want stuff fixed merge their changes into the
appropriate branch by Friday.
3. That person actually rolls a release on Friday.
4. People vote here on dev@svn
5. When there are enough +1s, the release is posted to
subversion.tigris.org
6. If there is a showstopper, then it gets added to STATUS
and the process begins anew when #1 occurs again.
Anything more complicated is asking for trouble, IMO. The release
cycle should take no longer than a week at the most.
This is also why I'm in favor of just having 3 +1s across all
platforms to do the release - not have 3 +1s on every single platform.
That decision has very strong negative implications on the length of
the release cycle. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 17:08:11 2006