On Wed, Feb 3, 2010 at 8:58 AM, Adrian Buehlmann <adr...@cadifra.com> wrote: > On 03.02.2010 15:51, Adrian Buehlmann wrote: >> So we might do >> >> 1.0.1000, 1.0.1001, 1.0.1002, .. for stable nightlies >> 1.0.2000, 1.0.2001, 1.0.2001, .. for unstable nightlies >> 1.0.0, 1.0.1, 1.0.3 ... for official releases >> > > Of course this should be: > > 1.0.1000, 1.0.1001, 1.0.1002, .. for stable nightlies > 1.0.2000, 1.0.2001, 1.0.2002, .. for unstable nightlies > 1.0.0, 1.0.1, 1.0.2 ... for official releases > > (too many similar numbers :-) >
Official releases would be 1.0, 1.1, 1.2 (just like hg) Patch releases would be 1.0.1, etc. If we're just talking about package numbers, not the version numbers that go into executables and DLLs, then I think I would prefer to take the 'tagdistance' number of the THG repo and add an offset based on stable/unstable So..1.1+42-62210b9542c8 would generate an unstable package with version: 1.1.2042 -- Steve Borho ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
