I'm not a big fan of using date information in the version number. Is there an advantage to doing that? Using a model like 0.0.1 makes it easier to communicate.
A better approach might be to use Major.Minor.Revision.Build. If we want to use dates, Year.Month.Day.Build or Year.Minor.Revision.Build might be a better approach. Do any openstack projects use the build number in the version? or is there a way for the build process to insert the build number in there? Thanks, Murali On Nov 14, 2013, at 8:23 AM, Noorul Islam K M <noo...@noorul.com<mailto:noo...@noorul.com>> wrote: Hello all, We need to decide on version scheme that we are going to use. Monty Taylor said the following in one of the comments for review [1]: Setting a version here enrolls solum in managing its version in a pre-release versioning manner, such that non-tagged versions will indicated that they are leading up to 0.0.1. If that's the model solum wants to do (similar to the server projects) then I recommend replacing 0.0.1 with 2014.1.0. Regards, Noorul [1] https://review.openstack.org/#/c/56130/ _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
