2008/12/24 James Tremblay aka SLEducator <fxrsliberty(a)opensuse.us>us>:
Rob OpenSuSE wrote:
> 2008/12/23 James Tremblay aka SLEducator <fxrsliberty(a)opensuse.us>us>:
I'm not sure an extremely polished 12.0 would be
viewed as "stale",
considering KDE4's status and the impending GNOME 2.28, we might even
get kudo's for taking the extra time to solidify 12.0 while we make a
"programatic" change to our delivery system.
This could even gain us ground in terms of the "it just worked"
comments. With this increase we would really be converting users to
openSUSE that see Ubuntu as having more "user acceptance" before
release. Bottom line, time taken to gain ground against the bugs isn't
It was later on in the 12 series, I was concerned about. Then having
12.0 as a stable release, then doing a big revamp for 12.1, and
restabilising for a 'final' at 12.3, seems to be mixing messages.
And KDE, well the missing functionality and useability issues are
hopefully going to be solved by new development releases 4.3, rather
than by bug fixes to 4.1 series say. There's no guarantee that taking
time, will result in something deliverable, that has both the
functionality expected, and is solid without need for many bugfix
How often is openSUSE meant to be 'delivering' a base for SLES/SLED?
The issues mentioned in the 11.2 schedule were :
- Need more testers, earlier
- Stability of release alpha releases was sometimes better than RC
- Need for development cycle time
- Trouble scheduling to avoid just missing releases of KDE & GNOME
- Some reviewers & testers, find 11.1 GM would have benefited from
more fixes for things found testing and feedback on usability
- openSUSE release, needs new cool things and up to date packages
to interest the Press
- users want it to "'just work"
I think I've understood this right, that 11.2 isn't destined for
SLES/SLED but in future
- good basis for SLES/SLED would be a requirement
Looking at all that, I think a possible solution, is a radically
different release model, one not based on evenly spread "releases"
throughtout the calendar year.
For 11.2, to summarise suggested proposal, as stands :
- development ongoing
- whole load of alpha's
- whole load of beta's
- 2 RC late in cycle (GNOME 2.28 not ready yet)
- Big Bang 11.2; releasing late autumn
I don't know why (apart from being helpful to openSUSE) I'd use an
alpha, or a beta there. Nor, whether I have to throw an install away.
Is it testing the installation process? New software versions?
Alternative "Creshendo" System, aims :
- more testing, more inclusion of changes based on user feedback
- more convenient for most users, 1 install or big uprade per year
to get to latest release
- each release of ISO's has a main focus, and the beta label can be
removed based on quality
- allows shipping stuff when it's ready, based on quality
- simple marketing message, you're using openSUSE 12.
- objective is to deliver up to date (latest KDE/GNOME), best
tested distro in Novemember
- 2 supported releases in 2 years, not 3
A hybrid of "Rolling Release" and traditional planned date based
release, to try and get the advantage of both.
Everyone on the same better tested version, at end of year; one that
would "just work" on wider range of hardware, and be a solid release
that can have better focussed support, during the 'development' cycle.
Where only Factory is unstable.
- Net Install ISO 12.0 early for early adopters, after couple
Alpha's, and Q1 Development
- "Current release" has rolling updates, so the user base grows
- ISO & Live CD 12.1beta with a KDE 4.3 beta? For installation testing
- ISO & Live CD 12.1, new KDE 4.3 (12.0 -> 12.1 via updates)
Net Release CD/DVD for K-er's
- ISO & Live CD 12.2beta with a GNOME-2.28 beta? For
- ISO & Live CD 12.2, new GNOME 2.28 (12.1 -> 12.2 via updates)
Net Release CD/DVD for G-er's
- 12.3 - usability improvements developed with feedback, bug fixes
(12.2 -> 12.3)
Net & Physical Media Very well tested upgrade 11.1 -> 12.3.
In that system, to upgrade "Release Version" (this needs changes
to Update Tools)
- apply all updates
- unlocks the upgrade to next Release Version, option (edit
/etc/issue and upgrade packages from new version)
When your system is not up to date, you are informed that there's a
new release, but online updates must be applied first. Via the
"updater" tool that tells you when there's security patches, and
updated software available.
The 12.0, 12.1, 12.2 only get short term support, once next release is
out, because every user is a net user who's accepting the "Current"
release, if they want support.
Those who want "stability" and minimum changes, ought to go with 11
series + security patches; until they're ready for OS 12.3.
Because the majority of development is done by, 12.1/12.2 stage, then
the development cycle for next release, can begin in the Autumn, with
aim to make it available for 13.0 late spring. That's a lot of time,
without worrying about general users, so should allow big changes.
Psychologically, I think more ppl will use the current version because
of "Rolling Release", and you're spreading out the load of end user
migration, by appealing to sub-sections of the user base.
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org