 |
 |
Hi Andy and all, since the last call I had a look at several existing project policies and it seems to me that classical major.minor.patch structure should work well and most users will have a reasonable expectation what a version change means. For a more formal definition of the change semantics in each number we could maybe adapt eg the simple approach described on http://apr.apache.org/versioning.html Cheers, Dirk On 17 Sep 2010, at 02:52, Andrew Hanushevsky wrote: > Hi Guys, > > From our last meeting we had an action item to come up with the svs (simple > versioning scheme). I have not seen any suggestions and it's getting to the > point we need a scheme pretty soon if we are to release a new version. So > please go at it! > > Andy >