Is there a uniform release policy for the ASF? For example, here are two documents:
http://httpd.apache.org/dev/release.html "Technically, any one can make a release of the source code due to the Apache Software License. However, only members of the Apache HTTP Server Project (committers) to project can make a release designated with Apache." The primary control has to do with the release "quality": alpha: "When a release is initially created, it automatically becomes alpha quality." beta: "at least three committers have voted positively for beta status and there were more positive than negative votes for beta designation." GA: "at least three committers have voted positively for GA status and that there "were more positive than negative votes for GA designation." No mention of PMC involvement, for example. On the other hand, Jakarta: "After a new release is built, it must be tested before being released to the public. Majority approval is required before the release can be made. Once a release is approved by the Committers, the Project Management Committee can authorize its distribution on behalf of the Foundation." - from http://jakarta.apache.org/site/decisions.html. Which is interesting, since most people apparently aren't aware that Jakarta sub-projects are supposed to get Jakarta PMC approval before distributing a Release. The XML Project has the same text as Jakarta, minus the sentence about the PMC requirement. I have no idea what other projects require. So ... finishing where I started: is there a uniform ASF policy on this issue? If so, what is it, and where is it documented? :-) --- Noel
