| > My proposal is that nightly builds should have a build number of the | format: | > 0.8.3.YYMMDD | > That way it's always clear that this is, in fact, a | development build. | > We should be able to add this to the daily build script to | > auto-increment. | > | | The revision number is actually a five digit number, so you | can't use the format you've described.. that's why I | mentioned YMMDD, and not YYMMDD |
If you are using the AL.EXE documentation, then, we still hit a hard limit of 0 through 65534 for the revision number, What happens after 2006 ? Can I suggest using the number of days since some reference date ? January 1, 2000, perhaps ? This should give us about 179 years to come up with a new revision numbering scheme. :-) We can try considering revision numbers less than 100 (or some arbitrary value) to be official builds, while anything else would be daily builds. Also using the leading 0's for 00001, doesn't really give you 0.8.3.00001. - Ants ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
