A message hit the opensuse-factory mailing list this morning, written by Kulow, and entitled "Calling for a new openSUSE development model." I was alerted in advance to the pending announcement yesterday in an embargoed email entitled "openSUSE to do some soul searching after delay of release."
What it's come down to is that the openSUSE 12.2 development releases have seen major delays due to broken packages and other problems. Every milestone has been delayed and now today they're delaying the first release candidate as well as the final release. Because of these delays and limited manpower, they're seeking out something different to do. Yesterday's private email also expressed, "[Kulow] believe believes the cause of the delays is a result of changes in the openSUSE community lately. We've grown and our current way of working doesn't scale anymore."
In yesterday's advance email, "This is a combination of a wakup-call and an opportunity to find new directions. We need to start working differently - and as we've got tools like OBS and initiatives like Tumbleweed, we are uniquely equipped among the major Linux distributions to do something new and different. Let's see where the discussions bring us."
Among the expressed ideas they started off with were abandoning release schedules for openSUSE, pulling back to releasing on an annual basis, and/or moving to a pure rolling-release model built around openSUSE Tumbleweed. Below are some of the ideas Stephan expressed in his public email this morning.
1. We need to have more people that do the integration work - this partly means fixing build failures and partly debugging and fixing bugs that have unknown origin. Those will get maintainer power of all of factory devel projects, so they can actually work on packages that current maintainers are unable to.A posting to be published in the next few hours on news.opensuse.org will lay out additional details and request for comments from the community about what future direction openSUSE should take.
2. We should work way more in pure staging projects and less in develop projects. Having apache in Apache and apache modules in Apache:Modules and ruby and rubygems in different projects may have appeared like a clever plan when set up, but it's a nightmare when it comes to factory development - an apache or ruby update are a pure game of luck. The same of course applies to all libraries - they never can have all their dependencies in one project. But this needs some kind of tooling support - but I'm willing to invest there, so we can more easily pick "green stacks". My goal (a pretty radical change to now) is a no-tolerance strategy about packages breaking other packages.
3. As working more strictly will require more time, I would like to either ditch release schedules all together or release only once a year and then rebase Tumbleweed - as already discussed in the RC1 thread.
What do you think openSUSE should do?