On Aug 5, 2005, at 12:08 PM, Mark Womack wrote:
I am going to build rc3 this weekend. We should treat that version
as the
final release candidate and move forward with final release,
hopefully by
the middle of next week.
If there are any concerns or issues, now is the time.
Thanks,
-Mark
I was a bit surprised to see HISTORY.txt having separate entries for
log4j 1.2.12-rc1 and rc2 since those builds don't have the
endorsement of the the project and will never be part of the official
history of log4j. In the next build, I'd wrap all the chances since
1.2.11 into one entry for 1.2.12.
I think that the proper location for distribution of the thing you
are building this weekend is http://cvs.apache.org/builds, not http://
cvs.apache.org/dist. The Releases FAQ (http://www.apache.org/dev/
release.html) mentions "release candidate" as a maturity state
following "alpha" and "beta" and not for a build that is being
considered for release. In that usage, we might have a log4j-1.3-rc1
issued after log4j-1.3-beta6 and before log4j-1.3.0, but all of those
would have required votes before being released. log4j-1.2.12-rc1
and -rc2 have not had official approval and would be considered only
builds, not releases, so they should go in /builds.
Have we had any reports, favorable or otherwise, from Chainsaw users
with the existing 1.2.12 release candidates?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
