> Although I agree, to be honest there is not so many people > contributing to pytrainer and therefore I don't expect tickets but > current distribution list regarding development version issues so I am > not really worried about.
Just to clarify, what I'm saying is that the version declared in trunk source should never be the same as a version that has already been released. Currently the version declared in trunk is 1.8.0 but that version was released a long time ago. > The reason for including revision number was to make clearer which > development version is running when making changes as it appears in > title bar. It's not that useful when it's not guaranteed to be up-to-date. Anyone running a dev version must have it checked out and the revision number can easily be obtained via "svn info". - 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
