On 2/1/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Feb 1, 2006, at 11:04 AM, Mark Womack wrote: > > > I'm pretty sure that I did not update to the latest site contents > > before doing the a8 build. Oversight on my part. If that makes a > > concrete difference, then we should -1 and do it again. > > > > (Have I mentioned that I really dislike having a dependency on a > > separate repo?) > > > > > log4j no longer depends on the "logging-site" module. However the > content on http://logging.apache.org/log4j is generated from the > files in src/xdocs.
Erg. This is still bad if someone updates the site before the release is approved and ends up copying up the modified download page. But ok. Seems like site release should be handled separately from project release. > > I did not see a SVN commit message and the contents and log for > http://svn.apache.org/repos/asf/logging/log4j/tags/v1.3alpha8/ > build.xml do not indicate that the "breakiterator" change and the > restoration of the DLL build. > > svn log http://svn.apache.org/repos/asf/logging/log4j/tags/v1.3alpha8/ > build.xml > svn diff http://svn.apache.org/repos/asf/logging/log4j/tags/ > v1.3alpha8/build.xml http://svn.apache.org/repos/asf/logging/log4j/ > trunk/build.xml I can't explain this. I guess my re-copying to the alpha8 tag did not work. There was a svn commit message on 1/30: Author: mwomack Date: Mon Jan 30 21:08:58 2006 New Revision: 373711 URL: http://svn.apache.org/viewcvs?rev=373711&view=rev Log: Tagging for 1.3 alpha 8 build Added: logging/log4j/tags/v1.3alpha8/trunk/ - copied from r373710, logging/log4j/trunk/ Is the "trunk" part for the tag messed up? > I do not see any reason in the current bylaws that the log4j-dev vote > and the pmc vote can not be concurrent. I do think that releases > need to be approved by the PMC, but it should not have to add any > time. Just post the call for vote on both lists. Just seems weird that the PMC might approve a release that the project rejects. > In this case, I would suggest: > > 1. Copy the contents of log4j/trunk to log4j/tags/v1.3alpha8 > 2. Update the contents of log4j/trunk/src/xdocs/download.xml and > other files to reflect pending release of log4j 1.3alpha8 > 3. Announce the results of the vote > 4. Prepare signatures for the tarball and zip currently on > cvs.apache.org > 5. Copy existing tarball and zip to dist server. > 6. Update http://logging.apache.org/log4j I tried to do #1 on 1/30 as part of the current build. There is still the issue of the FileWatchdog failure in Gump brought up by Scott on general. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
