On Fri, Aug 01, 2014 at 07:03:02AM +0200, Stephan Kulow wrote:
That's what I had in mind.
We still need to sort out when we pull from master into stable. David Sterba suggested waiting until the first -stable update for the next point release. So, e.g. Factory uses 3.15.X now and we wouldn't move to 3.16 until 3.16.1 was released.
I wouldn't do that. Factory is actually using 3.16.rc7 and beside the mkfs.btrfs OOPS I have no problem with it. I can live well without the RCs in Factory, but I would like to see problems as early as possible - - with the hope someone is actually fixing them too.
My idea is to be more conservative when the kernel is shipped to large number of users who do just 'zypper dup' and expect it to ~work. I hope that this will improve usability of a rolling distro in the long term People who want to test the .0 release could install from the Kernel:stable repository directly (I'll do that). When I'm aware of potential problems with new kernel, I'm also prepared to do a rollback to the last working kernel: setting up multiversion and keeping multiple kernels installed, bootloader points to the working kernel and I boot-once from the new one should any problems arise during boot. This excercise is natural to me because I work on kernel but I'm not expecting an average Factory user to set this up by default. The bad scenario I'd like to avoid is "I've updated Factory/kernel and it does not boot and I don't have a fallback". After such experience the users may leave Factory or just avoid updating kernel when there is a new release. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org