peter royal wrote:
On May 10, 2004, at 6:03 AM, Stephen McConnell wrote:

In the context of my inquiry, I couldn't care less whether Merlin even
compiles. We, James, are likely going to want to put out the next release after 2.2 using the merged code, and I want to make
sure that the released version of Phoenix, which is what James uses, works with these new packages

Phoenix compatibility is not a release criteria.

Do we have "release criteria" documented somewhere?

Yes we do.


Within the Avalon documentation you will find the following page http://avalon.apache.org/community/process/release.html which basically provides a bunch of links. The closest thing to "release criteria" is reflected in the opinion and decisions of the release manager. The is clearly documented under the HTTP release procedure documentation:

http://httpd.apache.org/dev/release.html

  Regarding what makes it into a release, the RM is the
  unquestioned authority. No one can contest what makes it
  into the release. The community will judge the release's
  quality after it has been issued, but the community can
  not force the RM to include a feature that they feel
  uncomfortable adding. Remember that this document is only
  a guideline to the community and future RMs - each RM may
  run a release in a different way. If you don't like what
  an RM is doing, start preparing for your own competing
  release.

Clearly, release criteria is what the release manager considers appropriate and necessary. In this particular scenario I'm the release manager and I consider that a success gump run against a _dead_ product as more than sufficient. Don't forget everyone can download and test the candidates against whatever they want - and from that - vote accordingly.

Stephen.

--

|---------------------------------------|
| Magic by Merlin                       |
| Production by Avalon                  |
|                                       |
| http://avalon.apache.org              |
|---------------------------------------|


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to