There's three issues regarding the version number I want to discuss. The first is simply that it should now be changed from 1.8.1 to 1.9.0 because a new feature has been added since 1.8.0 was released.
Secondly, the current version number in source code and the current version number in the bug tracker do not match. This should never happen - as soon as 1.8.0 was released the version number of trunk should have been bumped up to 1.8.1. I think we should have a formalised release procedure which documents things like this. Thirdly, that the version number is defined in main.py and manually includes the VC revision number means main.py is modified in every other commit. This makes browsing the main.py revision log extremely difficult - it made my job of searching for historical schema changes harder than it needed to be. In the long term we should move the version number to its own file. In the short term I would like to put a halt to the convention of including the SVN revision number in the trunk version number. Instead of "-svn#<rev>" I suggest we just use "-dev" as the suffix for the development trunk. This will dramatically reduce the number of commits made against main.py. - Nathan ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
