On 08/09/2010 12:33 AM, Gary V. Vaughan wrote:
By the reasoning I stated there, we should really have branched for 2.2 releases before adding any new features. So, if we want to release a 2.2.12, then we should make a branch at v2.2.10 and merge only fixes to it.
I don't think having a stable and development branch worked well with 1.5.x and 2.x. It added more work for us, and did not serve our users well - they had to wait years for the development branch's features to make it into a released libtool.
Developing new features etc. on a branch is, of course, ok, in my opinion (having to wait several years to merge is not so good though).
I don't really care what the version number is - as long as it's greater than the previous one :-)
Peter
