On Wed, 14 Mar 2007, Xavier Hanin <[EMAIL PROTECTED]> wrote: > I think it would be a good thing to produce a first incubating > version of Ivy early April, and I would like to check what we need > to do, and who does what.
We have a pretty detailed step by step guide at Ant[1] that show how we do it over there. In general the exact process of doing a release is different between ASF projects but there are a few things that are common: * the distribution must only contain stuff we are allowed to distribute * all non-project contents of the distribution must be properly attributed * all LICENSE and NOTICE files are in place (this also means inside the JAR file in the case of binary distributions), all project files contain the license headers * the distribution files are signed with a valid PGP key. Sidenote: make sure to catch Steve and myself (don't know whether any other Ant people will be around) as well as any other Apache people you will meet in Amsterdam and make sure we sign the key you intend to use for the final release. There probably will be a keysigning event at ApacheCon. * before the distribution files can be copied to the distribution area you need at least 3 +1s from PMC members and more +1s than -1s. * people will vote on the distribution files, so prepare what you want to release before calling for a vote. > So I would like to know what do we need to do to make such a > release. What is the process of releasing software in the incubator? It is not too different from the "normal" way of making a release AFAIU[2]. Your mentors are supposed to be Incubator PMC members, so our +1s should be enough to ensure the quorum. > Who can perform the remaining tasks? In theory anybody can be the release manager, being a committer certainly simplifies things 8-) Stefan Footnotes: [1] http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions [2] http://incubator.apache.org/guides/releasemanagement.html
