Re: Ubuntu 13.04 Still On Course for April Release?

It is pretty simple: an idea for a release management change was proposed to ubuntu-devel, and now we need to have a detailed, focused, and comprehensive discussion about whether it makes sense. These kinds of big changes take time to discuss and get right. If people are chomping at the bit for an answer, they are just going to need to wait a little until we reach a conclusion...this happens with every large proposed change in our community.

Edit: Actually, to be more accurate, the conversation itself was on Facebook:

Re: Ubuntu 13.04 Still On Course for April Release?

From my little understanding of how Ubuntu progress is mapped out, I would have thought that a suggestion like this should been a blueprint at the last UDS, the one for Raring if 13.04 was to become the rolling release. If it had not been for this idea of having an on-line UDS then this suggestion would have had to wait until the physically attended UDS for the 13.10. I am not much of an orderly person but it would make sense to me to get 13.04 out of the door and turn the 13.10 development release into the desired rolling release. This would not prevent discussion and planning and getting things in place in the meantime.

Regards.

It is a machine. It is more stupid than we are. It will not stop us from doing stupid things.Ubuntu user #33,200. Linux user #530,530

Re: Ubuntu 13.04 Still On Course for April Release?

Originally Posted by grahammechanical

From my little understanding of how Ubuntu progress is mapped out, I would have thought that a suggestion like this should been a blueprint at the last UDS, the one for Raring if 13.04 was to become the rolling release. If it had not been for this idea of having an on-line UDS then this suggestion would have had to wait until the physically attended UDS for the 13.10. I am not much of an orderly person but it would make sense to me to get 13.04 out of the door and turn the 13.10 development release into the desired rolling release. This would not prevent discussion and planning and getting things in place in the meantime.

Regards.

As anxious as i was for 13.04 to become the rolling, i have to stay, you make a LOT of sense...wish the developers that were at the UDS would read your comment here...
I get the sense that the developers of the community versions of ubuntu (like lubuntu) are getting po'd about the lack of answers as to whether 13.04 would be final released, because
they don't know if they should continue working on it..and most of us in the community also dislike the lack of definite planning with this...

Re: Ubuntu 13.04 Still On Course for April Release?

Just to make a quick a update, there is no change in schedule [1]
since the beginning of this cycle. We will push to have a Beta 1, and
a Beta 2, and a 13.04 release.

There is a lot of change ongoing on Canonical side. I'm still in the
process to analyse them and try to find the best way to adapt to this
new direction. But the priority is 13.04, we need to keep this in
mind.

I can't talk for Ubuntu, but for Lubuntu we are going to release 13.04, as
most of the flavors will do. When I do a schedule, I like to stay on track
during all the schedule. We decided 6 month ago to do a 13.04, I consider
we have to do this release. What Canonical want to do with their flavor
(Ubuntu) is their problem, not our.

I hope I answered your question. We will still have a lot of discussions
after 13.04 to see how we will handle the new model of development proposed
by Canonical, but let release this version first

So we know that both Kubuntu and Lubuntu plan to release as previously scheduled

Re: Ubuntu 13.04 Still On Course for April Release?

when tested stable.

Ah! That is most important. Some people think that "latest" = "greatest." And want it. And demand it. I think that sometimes there is an assumption by maintainers that whatever comes from upstream must be stable and it is merged without it being tested. In Linux the user is the tester but that should not be true in Ubuntu. During Quantal my OS was broken by an updated Nvidia driver that already had a serious bug reported against it. The same bug that I experienced. It should never have been merged.

I am in favour of Community Volunteer Testers testing code before it gets into the main branch. Or, if we are talking about the development branch having a rolling update, after it gets merged into the development branch but before it gets released as an LTS. There must also be a system where issues are reported back to specific developers and not lost in the big heap of bug reports. If a developer fails to fix the issues (and we are willing to test the fixes) then that "latest" code of his does not get into the LTS.

Regards.

Last edited by grahammechanical; March 9th, 2013 at 04:18 PM.

It is a machine. It is more stupid than we are. It will not stop us from doing stupid things.Ubuntu user #33,200. Linux user #530,530