incubator-heraldry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Querna <>
Subject Re: Release Cycle / Structure
Date Tue, 08 Aug 2006 16:59:47 GMT
The best page for how releases work in incubation is this:

But, its quite unfinished.

Here is the general flow while in Incubation
1) Vote on releases on heraldry-dev[1]
2) If vote passes, raise vote on general@incubator

Now, once Heraldry is out of Incubation, you remove step #2.

Expanding Step #1, from the general flow of how HTTPD Does it:
a) 3-7 Days before a "Release Manager" wants to do a release, send a 
courtesy message to heraldry-dev, telling other developers the intention 
to do a release. (And there is possible dissent here, enough to stop the 

b) Release Manager Tags the release in Subversion.  svn copy 
.../branches/1.2.x ../tags/1.2.3

c) Build release artifacts and cryptographically sign from the 1.2.3 tag.

d) Upload release artifacts to servers.

e) E-Mail heraldry-dev, with a [VOTE] subject line, voting to release 
1.2.3 with these release artifacts from tags/1.2.3. Insert URLs to 
download, and include crypto info in the email.

f) Close the vote after 3-7 days. Don't wait for specific people if they 
are on vacation, but if you tag on a Friday, try to give people until at 
least Tuesday or Wednesday to get around to testing the release.

g) If the vote passed, upload release artifacts to servers to 
be mirrored. If the vote failed, go back to part (a).

h) 24 hours after uploading to be mirrored, update the website with 
links to the downloads, and send out a release announcement email to, and potentially other lists.

Last Point: Who can be a release manager? Any active committer, at least 
in httpd land.  Some of the other ASF projects do 'assign' someone to be 
it for a branch (eg, 1.2.xx), but I personally find this distasteful.


Recordon, David wrote:
> This page gives a good overview of how voting works:
> --David
> -----Original Message-----
> From: Kevin Turner []
> Sent: Mon 8/7/2006 5:17 PM
> To:
> Subject: Re: Release Cycle / Structure
> On Wed, 2006-08-02 at 22:14 -0700, Recordon, David wrote:
>> We all understand there will be a different release process from today,
>> in terms of a vote for each release,
> Actually...
> It's probably best if I step up and admit my ignorance on this point
> sooner rather than later, as today I don't fully understand what the
> release process entails.  Can you point me to a primer on that?  Are
> there any other points of process than I need to familiarize myself
> with?
> Thanks,
>  - Kevin

View raw message