Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 21545 ideas, 132412 comments, 2606687 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #14812: Each release of Ubuntu could focus on a specific area

Written by rainwalker the 25 Oct 08 at 21:45. Category: System. Related project: Nothing/Others. Status: New
Rationale
The upcoming (as of this writing) release of Intrepid Ibex (8.10) had a huge focus on network connectivity. After trying out the just-released RC1, it seems that this has paid off!
What if, because of Ubuntu's relatively rapid release cycle, each new version focused mainly on improving one area? For example, assuming Ibex gets network connectivity to an adequate level, the next release could focus on improving sound. Even better, there could be some kind of vote or conference to determine what the priorities should be for improvement.
I'm not saying the developers should disregard developing the rest of Ubuntu, I'm saying that a certain focus could be put on intensely improving a certain area. Rather than improving bit by bit all-around, Ubuntu could improve greatly in different areas each release where it is most needed.

If you vote down, please say why.
If this is a dupe, I'm sorry, I searched and couldn't find one like it.
Tags: development

25
votes
up equal down
Solution #1: Auto-generated solution of idea #14812
Written by rainwalker the 25 Oct 08 at 21:45.
Ubuntu Brainstorm was updated in January 2009. Since the idea #14812 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

Propose your solution

Attachments
No attachments.


Duplicates


Comments
Deightine wrote on the 25 Oct 08 at 23:01
I like this idea. A lot.

Only issue would be that not all of the open source developers working in and around Ubuntu have skill in the same regions, so inevitably focusing on one thing without giving some of them years to build up skill, might lead to underutilizing volunteers.

But it definitely seems like a good idea. I could go for 1-2 development cycles devoted entirely to system speed and process integrity improvements. Boring to code, but vital.

alcockell wrote on the 26 Oct 08 at 08:45
Umm - would some of the major showstopping bugfixes be rolled into the LTS releases - if they don't muck up stability?

andruk (Idea reviewer) wrote on the 26 Oct 08 at 08:53
I like this, but only if the bugfixes are backported to LTS supported LTS releases, as alcockell pointed out.

Eldmannen wrote on the 26 Oct 08 at 14:19
They kind of do.

8.10 "Intrepid Ibex" focus was on network connectivity.

tchalvakspam wrote on the 26 Oct 08 at 14:25
I think that this already happens more fluidly via the current blueprints: https://blueprints.launchpad.net/ubuntu/intrepid

People submit things that need working on, and the important ones get essentially or high importance. This is much more dynamic than choosing a major topic beforehand and keeping to it. It -responds- to the current needs instead of deciding which needs to fulfill in the next release.

I think that topic based releases, in that light, would be less effective than the current system.

rainwalker wrote on the 6 Nov 08 at 05:44
Ohhh, thank you tchalvakspam, I didn't know it worked that way :)


Post your comment