On 02/05/2014 07:46 AM, Jonathan Aquilina wrote:
> Hey guys I think its an appropriate time to discuss the release cycle
> as well as How long are we going to support a version before we end of
> life it.
>
> Looking forward to hearing your thoughts about this.

Are we even going to have different version branches? Has this been
discussed yet? I thought we were just going for a rolling-release model,
ie. each version is supported until the next version...

But I guess it also depends on the definition of "support". How are we
planning to support each release? Does "support" simply mean releasing
bugfixes for?

If we look at a software like GIMP for example, they have two main
branches: the even-numbered stable branch, and the odd-numbered dev
branch. The stable branch only gets bugfixes, no new features, while the
dev branch gets all the cutting edge feature additions. When the dev
branch becomes stable enough and meets all the goals in the roadmap, it
becomes the next stable branch and the old stable branch goes EOL.

I guess we could go for something similar, but I don't know if we're
really big enough yet for that to make sense... I don't know if there's
any advantage in a stable version that doesn't get any new features? We
already sort of have this in that official releases are like the
"stable" branch, while getting the latest from git is the "dev"
branch... and that approach may actually make more sense for us, if we
want to maintain a fast pace for releases.

I guess it comes down to whether we want to release small bugfix updates
to earlier releases, even when we're already working on newer ones? Or
should we expect users to always be using the most recent release?

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to