On Tue, 11 Dec 2012 19:19:42 +0100 Togan Muftuoglu <[email protected]> wrote:
> On 12/11/2012 06:47 PM, Pascal de Bruijn wrote: > > On Tue, Dec 11, 2012 at 6:38 PM, Pascal de Bruijn <[email protected]> > > wrote: > >> On Tue, Dec 11, 2012 at 5:49 PM, parafin <[email protected]> wrote: > >>> On Tue, 11 Dec 2012 17:31:58 +0100 > >>> Togan Muftuoglu <[email protected]> wrote: > >>> > >>>> Thanks for the info, was helpful, but I think Pascal and I are on the > >>>> same boat as for providing a nightly release based on the git master one > >> > >> Yep. And I guess we both don't like the boat we are on :) > > >> > >>>> , at least speaking of myself, tries to get a version based on the git > >>>> describe and as far as I can tell this is the same logic used by the > >>>> create_release.sh in the tools directory. > >>>> > >>>> For the time being I am just changing the archive to be > >>>> 1.1.1_gitshawhatever and using this as the versioning for my nightly > >>>> builds > >>> > >>> 1.1.9999 version was suggested by someone for git builds (with > >>> appropriate suffix), which I adopted for OS X package (if I or someone > >>> else decides to do non-release DMGs in the future). Calling them 1.1.1 > >>> isn't right... > >>> 1.3 of course looks much cleaner and I for one vote for appointing this > >>> version to current git master. > >> > >> I'd be fine with both of the above. But some standardization is > >> definitely in order. > >> > >> Though the latter does apply a change in general versioning: > >> 1.3.x is development phase of 1.4.0 > >> 1.4.x is the stable patch release tree of 1.4.0 > >> 1.5.x is development phase of 1.6.0 > >> 1.6.x is the stable patch release tree of 1.6.0 > >> 1.7.x is development phase of 1.8.0 > >> 1.8.x is the stable patch release tree of 1.8.0 > >> yadiyadiyada > > Maybe a better solution, just a thought, is to follow a structure as > outlined in <http://nvie.com/posts/a-successful-git-branching-model/> > > This approch could help us solve the versioning issues for us,the > nightly package builders There's nothing in there about patch releases so what's exactly you're proposing? Just don't do them? Or always release git master? That won't work for us. > > Togan > > Togan > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > darktable-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/darktable-devel ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
