Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 21986 ideas, 135057 comments, 2615221 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #23624: Consider a one year release schedule

bug This idea is a duplicate of Idea #15245: Have longer test and release cycles..
Written by jjchico the 9 Feb 10 at 16:49. Category: Quality. Related project: Nothing/Others. Status: Awaiting moderation
Rationale
With every new Ubuntu release we get cool new stuff but also get regressions, important bugs not solved yet and so on. I normally recommend using the "previous" not "last" Ubuntu release for that.

Besides, I usually update my systems during late alphas and I report bugs that are not fixed for release because the debugging period during beta is very small (e.g. release candidate is only there for one week before final release!).

New (and also experienced) Ubuntu users are frequently disappointed because they are affected by bugs that will only be solved far beyond the release or simply have to wait for the next release because (I understand) developers are little motivated to solve a bug in release X when X+1 is out in one or two months.

More and more Ubuntu users claim it is not recommended to use Ubuntu just after release but wait for two or three months to get most important bugs solved. What is the point in releasing every 6 months then?
0/1
Approvals

0
votes
closed
Solution #1: One year release schedules with 6 months beta/RC testing.
Written by jjchico the 9 Feb 10 at 16:49.
Planning should be like this:

* After a new release (Ubuntu X), X+1 develops in a similar way it is done now.

* About 4 months after release there is a (maybe soft) feature freeze and alpha cycles start. Developers and more advanced users start using alphas everyday.

* About 6-8 months after release, first beta is published. Developing concentrates in release bugs. Experienced users start using betas everyday.

* About 8-10 months after release, first RC candidate is published. Normal users that want to test the new system are encouraged to update to the RC and report bugs. There is time to solve important bugs before final release.

During beta and RC cycles, core developers can start the basis of the next release (X+2) so the overall progress of the distribution do not need to be affected, specially when you do not need to produce a release every 6 months.

Propose your solution

Attachments
No attachments.


Duplicates


Comments
jjchico wrote on the 10 Feb 10 at 11:14
Idea #15245 is similar, but this one is not a duplicate: it separates the problem from the solution and rationale focus in different aspects.

It is not just a longer release cycle, it is just one year release cycle and I explain why.

#15245 is rather old and it is not visible (I look for duplicates before posting and could not find it).

DeMus wrote on the 22 Oct 11 at 09:33
This is a great idea. I posted the same here:
http://brainstorm.ubuntu.com/idea/28733/
The way the releases are handled now is developers work on 5 different versions, one new and 4 they still have to maintain. Ridiculous.
With a once a year system there are only 3 versions still in operation, giving more time to the developers, plus they have more time to make the new version, giving a better product. One you can use from the release date on and not only after several months.


Post your comment