Stephan Kulow <coolo@novell.com> writes:

I try to line up 11.4 early as I think we need to start discussions around milestones early as there are quite some holidays ahead in our way - so if you have suggestions to make or plain feedback to give, feel free to put it in nice words ;)

I'm not that sure what you want to hear here ;) I think we should spend more time on testing "upgrading the system" (such as from 11.2 to 11.3, or from 11.3 to 11.4). I'm upgraded from 11.2 to 11.3 yesterday using yast and encountered some issues. 1/ gconftool is still ugly slow (bnc#555827). 2/ automatic rebooting after the basic upgrade did not work, at one point I have had to press the power button. 3/ After all the upgrading was done, I have had to reboot on my own again, because the keyboard did not work as expected (I guess "init 1" and "init 5" would have done the trick, too). 4/ For consistency reasons, yast messages need some adjustments (s/update/upgrade/) to match the terminology used by zypper... Since all this was thus slow (see 1/), I did not have the time to write proper bug reports. Thus my suggestion is to spend more time on testing the system upgrade process. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Jul 20, 2010 at 10:39:49AM +0200, Stephan Kulow wrote:

Hi,

Factory has opened up again and already sees tons of broken packages :)

I try to line up 11.4 early as I think we need to start discussions around milestones early as there are quite some holidays ahead in our way - so if you have suggestions to make or plain feedback to give, feel free to put it in nice words ;)

Greetings, Stephan

I do have some plans there. Of course, I will keep running my daily automated factory snapshot install testing which already helped to spot issues before they made it into milestones and RCs. But I was also thinking to use the Qemu snapshot feature to easily use a read-only base-image of a stable release to test zypper dup on a regular basis. zypper dup from last MS is certainly also worth testing as this is what testers will do and thus should not fail. Maybe I will even include a rolling zypper dup from Factory to Factory. As for the discussion part, I would not mind having more releases during the stabilizing phase (e.g. last 3 months before GM). E.g. RC1 and RC2 were only 2 weeks apart, so why should milestones before that be 4 weeks apart? Let us say, Milestone MSn is released on day x on day x+3 to +7, most testers will have upgraded to MSn, then some days to spot+report the most obvious issues => x+9 then some days to bugfix => x+13 and until the package is rebuilt => x+15 retested and uploaded to Factory => x+17 leaving some margin until next Milestone MS(n+1) => x+21 so a release cycle of three weeks could be possible. While we had MS5-7 during 11.3 stabilizing, there could be MS5-8 for 11.4. for reference, old 11.3 Roadmap looked thus http://old-en.opensuse.org/Roadmap -- Bernhard M. Wiedemann software engineer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org