Many people have noticed that the milestones and the Beta for this openSUSE release have been delayed or even canceled like Milestone 4. Now the RC is planned to go out Thursday – but that seems unlikely to happen as Factory, our development project, is still far too unstable. Coolo has send a mail to the openSUSE Factory mailing list noting that we need to re-think how we’re working.
We need new ideas
The mail by Coolo serves as a wakeup-call for openSUSE. Right now, we work via the devel projects which collaboratively send in better packages to Factory. But even then, sometimes things break in major ways and this breakage has gotten more frequent over time due to the growth of our community. One solution for this is to make heavier usage of ‘staging projects’ where packages get deeper testing and more integration can be done before moving to Factory. Another direction we could take is building more on our strengths like OBS and Tumbleweed. Slowing our release cycle to produce more stable releases say once a year, while increasing the emphasis on and efforts put in Tumbleweed and our OBS repo’s with newer software could give both ‘bleeding edge’ fans and those depending on a stable openSUSE more of what they want. Or, we go and loosen our release schedule, bringing out openSUSE ‘when it is ready’.
All options have pro’s and con’s. We want to avoid loosing ourselves: introducing rules and procedures to solve problems isn’t our way. So, we need fresh ideas and look in other directions. And now is the time to discuss these things: we’re bumping into the limits of how we work so the sense of urgency is there!
Limits: delays and cancellations
Pretty much every milestone of openSUSE 12.2 has been delayed or even canceled. Compared to the preliminairy schedule, milestones 1 to 3 were only about one to two weeks late – but milestone 4 had to be canceled and even Beta 1 was 2 weeks late. Release candidate 1 won’t make it either – to get Factory close to a releasable state we’d need to think about a serious delay.
The milestones faced the usual issues. Sometimes, the Buildservice goes down – and with the huge amount of development going on there it takes a while for it to churn through its backlog and catch up again. Another issue were some problems with the integration of some of the bigger features – most notably GCC 4.7 but also Automake are still creating big pains. And in general, the stability of openSUSE Factory is not exactly up to our usual standards, as many threads in the Factory Mailing list Archive show.
But these integration issues are not just incidental but, according to release manager Coolo, exposing deeper problems. openSUSE contributions have grown in the last few years but the way we used to work doesn’t scale to our current size.
With more new contributors sending in bigger and small(er) improvements and quite a bit of plumbing going on in openSUSE, problems are arising. All these changes need to be combined, integrated, made a whole. Some people need to look at the big picture. This doesn’t happen at the rate it should be so things in Factory are broken more often than not. This leads to a bit of a broken-window problem: the more is broken, the less people care and the harder it is to get anything done – discouraging contributors. Say hello to a downward spiral.
All this has gotten us to the point where the release manager doesn’t feel confident that we can release openSUSE on time. Actually, Coolo says something needs to change if we are to do even remotely timely releases at all. Looks like a challenge!
We need to take the time to think about this and change things. The release will be delayed, that’s for sure. But how are we gonna tackle things in the future? As we’re grown too big for the current model, we have a great opportunity to find new ways.
Just more people won’t solve it. Especially things like bigger changes to the tool chain simply need a crew of highly experienced core hackers to fix issues all over within a reasonable time frame to avoid the ‘Broken Windows’. While we call on people to step up, we also need to look in other directions.
Release schedules and staging projects
We could drop the fixed release schedule and release ‘when ready’. But this could lead to long freezes (a la Debian), uncertainty for the users and either out of date packages or huge discrepancies in quality.
Coolo says that giving up on releases altogether, making openSUSE a tumbleweed-on-SLE would work as well. But – to mention just one issue with this scheme, Tumbleweed needs to rebase on new releases as it’s not designed to roll forever. So it would depend on new SLE releases for major plumbing work which, in effect, simply moves the problem to SUSE.
Another step we might have to take is look closely at how we work. Working more in staging is what Coolo proposes. Working in the Devel projects is great but leads to integration issues. Working with more staging projects will need tooling support and won’t solve everything, but it is a step in the right direction.
The solution might be found in any of the above directions – or all of them. A possible scenario is to slow the release cycle a bit to one year releases (probably somewhere in April) and become even more conservative with those: the releases would contain changes, but only well-tested and stable new technologies would make it in. Meanwhile, we’d emphasize Tumbleweed and the OBS repositories more as the way of getting the latest and greatest of what Free Software has to offer. We’d also have to change how we work, introduce the staging projects, maybe improve certain parts of the OBS workflow. For end users, we might possibly release ‘snapshots’ of Tumbleweed or experiment with what we could offer through SUSE Studio.
If it works, this scheme would mean a lower workload for the release team and more choice for our end users: more stable (the release) and more up-to-date (tumbleweed). Like all major changes, it’s risky and requires quite some thought on the details. But the end result could be a better, even cooler openSUSE!
As a community project, openSUSE is led by people willing to take on a role where they make a difference. Those people are the ones who should chime in now and point in what direction we need to go. Coolo calls on everyone to
discuss things very openly – I think we learned enough about where the current model works and where it doesn’t so we can develop a new one together.
There’s a challenge ahead for openSUSE, an interesting one at that. What will we do? The discussion on the Factory mailing list is only now starting and we won’t have a decision any time soon. One thing is certain: the openSUSE 12.2 release won’t see the light of day on July 11th but we’ll come with something cool for the future!
Both comments and pings are currently closed.