Hi, Soon I want to start pushing git master packages again, however once again I have versioning issue (like any packager would).
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 proposal is to an alpha release (possibly this weekend), which means a 1.2~a1 tag will be created so this has several advantages: 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) Also, this makes it more obvious for users that the git master branch will be 1.2.0 not 1.1.3 :) And this also means the noise profile script can use darktable --version to check if the profiled denoise module is present. Regards, Pascal de Bruijn ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
