I remember Geoff talking about how much work it is to cut releases, and also about all the places where version numbers need to be updated.
So, in the interests of making it easier to release, I'd like to spend a bit of time automating part of this procedure. Specifically, I want to eliminate hard-coded version numbers where it's possible (and desirable) to do so, and I'd like to write a utility which will automate updating all of the other places (BumpVersion, a companion to ReleaseHelper). I've also thought about tweaking the procedure for making release notes slightly. I think it would make sense in each Doc directory to have a RelNotes-HEAD.html (generated from RelNotes-HEAD.txt, once we complete the switch to structured text). As we add new features during the development cycle, we should be adding to these release notes at the same time we commit the features/fixes. I know some developers do this already -- let's update the documentation to reflect this procedure. When BumpVersion is called, it will rename each RelNotes-HEAD.html to have a specific version number (say RelNotes-0.8.html, for example), and create a new (empty) RelNotes-HEAD.html for the next development cycle (I'm literally talking about using the string "HEAD", because at that point we don't necessarily know what version number we will give to the next release). BumpVersion will be smart about renaming release notes for alpha/beta releases; a bump from 0.7 to 0.8b1 would do the above-described renaming, whereas a bump from 0.8b1 to 0.8b2 would rename RelNotes-0.8b1.html to RelNotes-0.8b2.html. This would be the correct behaviour, right? Let me know what you think of this idea. No feedback defaults to "sounds ok, go ahead with this". :) cheers, -- Jason D. Hildebrand [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
