Hi,
concerning the log4cxx release process :
- First you should vote on the dev mailing list and report the vote result to [EMAIL PROTECTED] - Please consult http://www.apache.org/dev/ for further official stuff.
This is the non official release process :
Release binary ==============
- Make sure all new features and fixes have been tested with unit tests (directory logging-log4cxx/tests) - Make sure all the tests pass on officially supported platforms by invoking 'make check' - Eventually, add new supported platforms to logging-log4cxx/README - Eventually, complete logging-log4cxx/INSTALL with instruction for compiling on new platforms. - Review in the log4cxx-dev mailing list archives all the cvs commits since the last release and make sure that a JIRA issue has been created and closed for each. - Complete file logging-log4cxx/ChangeLog with JIRA issues concerning the new release - Increment version number in logging-log4cxx/configure.in (macro AM_INIT_AUTOMAKE) - Increment Libtool version number in logging-log4cxx/configure.in (macro LT_VERSION) - Commit configure.in, Changelog, README and INSTALL files - Build the version with 'make dist' - Log to www.apache.org with 'ssh [EMAIL PROTECTED]' - Copy the new release log4cxx-???.tar.gz to /www/www.apache.org/dist/logging/log4cxx/ - Create the checksum file with 'md5 log4cxx-???.tar.gz > log4cxx-???.tar.gz.md5'
Update Web site ===============
- Make sure you have checked out logging-log4cxx and logging-site (main http://logging.apache.org site) under the same directory - Add to file logging-log4cxx/xdocs/src/news.xml a paragraph concerning the release version - Add to file logging-site/src/xdocs/site/binindex.xml links to the new binary and its md5 file. - Eventually, add new supported platforms to logging-log4cxx/xdocs/src/index.xml. - For the moment, you must generate manually a Doxyfile from logging-log4cxx/xdocs/src/manual/Doxyfile.in - For the moment, the files logging-log4cxx/xdocs/src/manual/header.html and footer.html must be updated manually in order to reflect the site menu in the Doxygen documentation. - Build the logging-site html files by invoking 'ant' from the directory logging-site - Build the logging-log4cxx html files by invoking 'ant' from the directory logging-log4cxx/xdocs - Log to www.apache.org with 'ssh [EMAIL PROTECTED]' - Go to directory /www/logging.apache.org/site and check out binindex.html by invoking 'cvs update binindex.html' - Go to directory /www/logging.apache.org/log4cxx and check out the whole site by invoking 'cvs update'. you should at least check out the whole Doxygen doc and the news.html file.
Fresh meat ==========
Please create an account at freshmeat.net and I will add you as an admin to the log4cxx project - Add a new log4cxx release at http://freshmeat.net/projects/log4cxx/
Hope it will help.
Take care,
Micha�l
Curt Arnold wrote:
On Nov 3, 2004, at 12:10 PM, Christophe de VIENNE wrote:
I think we should try to make a release quite soon. I know that some issue remains, but if we want the lastest modifications to be correctly tested, a release is necessary.
Curt, could we try to plan this after APR integration ?
I also wanted to inform you that in 2 weeks I'll be out of office for 2 months. during the period I'll should be able to work a bit on log4cxx, but on a very irregular base.
I think it is quite reasonable to get the APR modifications and the TimeZone modifications in the next week. I'd also love to get Unicode related issues in, but it may be too much to get in within that time frame.
I have had no experience with the release process and with Micha�l's upcoming absence may make it necessary to get some help from another project, perhaps APR, to help us through the release process.
-- Micha�l CATANZARITI log4cxx project manager
log4cxx user mailing list:
mailto:[EMAIL PROTECTED] log4cxx developer mailing list:
mailto:[EMAIL PROTECTED]
