DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26677>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26677 Provide more version number granularity in manifest.mf ------- Additional Comments From [EMAIL PROTECTED] 2004-02-05 12:35 ------- We are now following the release system used by Apache HTTPD, Jakarta Tomcat, and many other projects. Once a release is rolled, it assigned a point number that never changes. Version 1.2.0 will start as an alpha release, and then we will vote to promote it to beta or General Availability. But the release number will never change. Regardless of what happens with 1.2.0, the next release will be 1.2.1. You are right in that we should probably attach a tag to the nightlies, such as DEV or SNAPSHOT, prior to the release being rolled. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
