On Fri, 2016-12-23 at 17:15 +0100, Andreas Schneider wrote: > An alternative would be to introduce an additional fourth number for the > development versions, e.g. representing the date. For instance, a build > from today would be 2.1.15.20161223.
That would involve changes in the C programming to determine if a new version was an upgrade. And it would not give a neat solution for the real (though slight) problem of exactly which was the last commit included in the build - see my other email > > At the moment, I am setting the version of my builds by hand. In which case, you could adopt the 2.0.x idea as in my other email, where a literal "x" is used to mean one of the unstable series. You would do the same amount of hand setting, just not giving the file a specific micro number. Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
