On 01/16/2013 10:18 PM, Pascal de Bruijn wrote: > Hi, > > Soon I want to start pushing git master packages again, however once > again I have versioning issue (like any packager would).
Seems like we are hit by this version theme often as packagers who are also providing nightly builds. > My PPAs now have 1.1.2, so I can't push a 1.1+gxxxxxxxx package, since > 1.1.2 is higher, and I can't go backwards. My nigthly builds are using something along the lines 1.1_734_g3498510 > > My proposal is to an alpha release (possibly this weekend), which > means a 1.2~a1 tag will be created so this has several advantages: Do you mean creating a branch similar to the 1.1.x type or just a tag, > > 1.2~a1 is higher than 1.1.2 so I can do git master builds on my PPAs again. > > 1.2~a1 is lower than 1.2~b1 (if we want to do beta releases as well) > 1.2~b1 is lower than 1.2~rc1 (when we start doing release candidates) Then when 1.2 is relased we go back to the problem of above so why not use 1.2.0~a1 as the starting point and then use as 1.2.0~a1 1.2.0~b1 1.2.0~rc1 > > Also, this makes it more obvious for users that the git master branch > will be 1.2.0 not 1.1.3 :) Togan ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
