i like this idea, paul. perhaps the version could be tagged something indicating 'development' between release tags, for example: '2.3.0- beta', and then once robert gets to his release point, changing to '2.3.0', tagging, and then immediately changing to '2.3.0-beta'. or maybe this immediately post-release version number is something like '2.3.1'.
ruminate... bob On Dec 12, 2007, at 5:00 PM, Paul Martz wrote: >> I'll bump the version number up once I tag the 2.3.0 release, >> I've been hanging back while more testing is carried out. > > Can I suggest a change in policy? The version number should get > bumped as > soon as the first post-release change is committed. At that point, > the code > no longer matches the previous release; the version number should > increment > to reflect that. > > If the SVN head version number contains post-release changes but the > version > number is unchanged, then code written for specific releases might > not run > on the current SVN head, thus delaying testing. > -Paul > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
