On 18 January 2014 16:54, Tobias Doerffel <[email protected]> wrote: > Hi, > > I'd like to plan the next releases and also propose to change the versioning > scheme: > > YY.QQ.RR > > YY=year > QQ=quarter (start counting at 0) > RR=release (start counting at 0) > > so if we manage to push out a release in January (which is my goal) it would > be 14.0.0. I know this would be a confusing jump the first time but I see > the advantage that we do not have to debate on what evolutionary step > justifies which version jump (when do we have 0.5, when 1.0, ...???) and > people can estimate easily how old their version is. Any opinions on this?
Yes, it seems like a nice idea even though it may be abrupt jump for people initially but thinking of a long run it certainly seems nice. I vote for this. > Concerning next releases I propose to concentrate on bugfixes only for the > stable-0.4 branch (which should be forked to master as soon as we made it) > and finalizing our initial UI improvements. This should be done until next > weekend. <snip> > Suggested roadmap for existing features branches (which IMHO are not mature > enough for inclusion in 14.0.0): > > * 14.0.1: merge stable-0.4-new-fx-mixer, maybe automation recording > * 14.0.2: merge stable-0.4-undo-redo > > Any comments and additions welcome! So we have till next weekend to add new features and solve bugs if we want to include them in the release? I should start working then. :D -- Gurjot Singh Blog: http://bhattigurjot.wordpress.com ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
