Actually many complained that 11.1 had a too short release cycle - so
they did not really start testing because they hardly finished their 11.0
polishing and I guess that's right for many. And if you go with a may
release with many developers having prolonged christmas holidays and ask
for an extended RC phase to stabilize and translate, this gives very
little time over a kernel and a gcc update. Does pretty hard to sell to
users to me.

I agree with them. I tend to prefer longer release times, particularly
from a testing (some people like to use their shiny new release before
they go bug hunting in the next one ;-)), and from a marketing
perspective (2 to 3 releases a year, every year gets tedious to manage,
and overwhelms users).

I think the current openSUSE schedule (which has been described to me as
"3 releases over a period of two years", is that about right?) is a good
pace.
--
Kevin "Yeaux" Dupuy - openSUSE Member
Public Mail: <kevin.dupuy@xxxxxxxxxxxx>
Merry Christmas & Happy Holidays from the Yeaux!

What about a longer release cycle but with a more flexible approach to
backports?
I'm thinking about kde 4.0 vs kde 4.1 in opensuse 11.0:
4.1 has been REALLY working better than 4.0 and could have replaced kde 4.0 in
opensuse 11.1. Yet it stayed in the factory repository untill 11.1...factory
repository is not the "official" one and there are issues from time to time
(and tons of updates everyday!). I propose for 11.1:
kde 4.2 comes out. Packages are built and go in kde factory repo. After a
period of testing (2 weeks?) if there are no big problems, they can go in kde
stable repo. After another 2-4 weeks, they go in the official opensuse 11.1
update repository. Same for gnome: This way opensuse releases won't be linked
anymore to desktop environments but on real improvements in the distro itself.
We have the great power of build service and we can use it this way.
What do you think about this?
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx