On Tuesday, September 11, 2012 12:31:57 Will Stephenson wrote:
On Tuesday 11 Sep 2012 11:53:08 Andreas Jaeger wrote:
* openSUSE 12.2 original schedule + 8 months = openSUSE 12.2 actual release + 4 months = Do a short cycle and release in March 2013, essentially 12.2 + bugfixes and updates
We already have many changes in Factory, so it's more than 4 months of development. : :D :
* openSUSE 12.2 actual release + 8 months = May 2013, business as usual, using a fixed process to solve the problems that caused the 12.2 slip
We've done the 8months cycle with these months so that it rolls perfectly round. If we stay with 8months and go to May it's: May, January, September. And January and September are both bad months for releases since the months before nothing happens.
A very good reason for keeping and sticking to the cycle we have, and one that that people easily forget.
* Change the process to plan more features in advance (as much as this is realistic given we mostly ship what our upstreams deliver) and work together to achieve these
Independed on the schedule, I think it's a good idea to discuss what features we do for the next release. The systemd discussion on opensuse- factory already lead to this webpage: http://en.opensuse.org/openSUSE:Goals_12.3
Takeaway from that to all teams: discuss your goals for 12.3 on Factory then add the outcome to that page; it's all the process we have for now.
I'm fine with some more planning and goals. It's not only shipping what upstream delivers but also changing defaults and how to integrate upstream stuff.
BUT I see one project that IMO needs to be in the next release - UEFI secure boot. I would make a schedule that allows that one to go in and even slip if it's not in. So the question to Olaf and Vojtech: When do you expect that we have something in openSUSE?
Coolo: QED ;)
AJ: why is this so important that you would sacrifice the time based release?
This is IMO a critical hardware feature. I expect that all new hardware in the lifetime of 12.3 will have UEFI Secure Boot enabled and we need to solve that. Releasing - like 12.2 - with only the option to go into the BIOS and disable it - is IMO the wrong approach. I expect 12.3 to have an implementation - and 13.1 further improvements based on the experience we made with UEFI secure boot, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org