I took a stab at the auto-version numbering, rolling the version to X.Y.
The release notes files RelNotes-X.Y.html have all been created and are
basically empty ready to be filled in for the next release. We can
re-name them when we get ready to build a new release.
There is now a bin/setversion.py script that forces the version
information in all Properties.py files, as well as .html files and .txt
files.
The .txt files (reStructuredText) had to use a different pattern match
on the version and release date because embedding HTML comments ended up
not working.
I'll update the ReleaseProcedures soon with information on how to run
this when it is needed.
If you install from CVS, the version number will be X.Y and the release
date will be @@/@@/@@. I verified this through the generated indexes and
components list when install.py is run as well.
I'm not sure this is the complete solution here, but it is a start, and
it eliminates some confusion between the tip of CVS and the latest
released version.
-Stuart-
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
