On Mon, Nov 21, 2011 at 5:23 PM, Duaine Hechler
I - LOVE - Linux and I - LOVE - openSuSE although, I have to pose a question:
Are the developers forcing the (I believe ?) 8 months cycle and falling down on the QA testing before the rollout ?
Eluding to: My wife works is a contract QA tester and on several occasions she has been told that - basically the hell with QA testing - we HAVE to meet the target rollout date - and - those little errors can be fixed later.
Is this happening - or - am I wrong ?
Duaine
P.S. Still going to use openSUSE anyway !
Duane, It is more like: openSUSE has thousands of moving parts, freezing development of new functionality for a couple months to debug and fixing the relatively few broken packages drastically slows down the process, so instead opensuse follows a model like: 1) allow major/core updates (about 4 months) 2) allow minor/leaf updates (about 2 months) 3) freeze and allow only debug updates (about 2 weeks) 3.1) split off a release from the main dev repos (factory). Allow factory to accept major updates again. 3.2) accept only debug fixes into the now split off release repo. (about 2 weeks) 4) check for any bugs that can't be fixed by the update mechanism (ie. showstoppers) 5) If none, declare a a Gold Release and ship 6) push out fixes to the bugs via patches The above really is fairly accurate. You will note that the only showstoppers are things that can't be fixed via patches. So people's assumption that the openSUSE release schedule targets a bug free release is simply wrong. Instead, when a new release comes out users should monitor the most annoying bugs page and make sure they feel comfortable with the major bugs they see before they jump in and upgrade. ie. There are lots of opensuse packages I don't use, so most of the annoying bugs don't impact me. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org