Re: [opensuse-factory] feature freeze dates for 10.2
jdd@dodin.org 10-08-2006 14:45 >>> In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates...
One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome)
I think the latter are already tested by they developpers when the first seems already in a very early stage.
I'm disquieted by the "most annoying bugs" list and the _may be_ delayed Alpha 3.
I personnally think that a stable distribution is better .than the very most up to date one.
Hi, I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3). The worst that can happen to openSUSE is having (again) a release with bugs like the updater in 10.1. Even though they are fixed now, it's still around and poeple installing without an internet connection most obviosuly run into it. If the schedule for 10.2 should be kept like this (which I think it should) then we should try to put bugs away instead of adding last-minute-features and packages. Some might be solved with new packages, some might not. Dominique
On Thu, Aug 10, 2006 at 02:29:36PM +0200, Dominique Leuenberger wrote:
jdd@dodin.org 10-08-2006 14:45 >>> In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates...
One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome)
I think the latter are already tested by they developpers when the first seems already in a very early stage.
I'm disquieted by the "most annoying bugs" list and the _may be_ delayed Alpha 3.
I personnally think that a stable distribution is better .than the very most up to date one.
Hi,
I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3).
We have Alpha3. Bugs are expected ;)
The worst that can happen to openSUSE is having (again) a release with bugs like the updater in 10.1. Even though they are fixed now, it's still around and poeple installing without an internet connection most obviosuly run into it.
If the schedule for 10.2 should be kept like this (which I think it should) then we should try to put bugs away instead of adding last-minute-features and packages. Some might be solved with new packages, some might not.
Its definitely not last minute for 10.2 yet. CIao, Marcus
On Thursday 10 August 2006 15:27, Marcus Meissner wrote:
On Thu, Aug 10, 2006 at 02:29:36PM +0200, Dominique Leuenberger wrote:
jdd@dodin.org 10-08-2006 14:45 >>>
In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates...
One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome)
I think the latter are already tested by they developpers when the first seems already in a very early stage.
I'm disquieted by the "most annoying bugs" list and the _may be_ delayed Alpha 3.
I personnally think that a stable distribution is better
.than the very most up to date one.
Hi,
I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3).
We have Alpha3. Bugs are expected ;)
Perhaps replacing Alpha with Devel would convey the right message to people, that these releases are development releases that are not feature-complete or in feature-freeze. After feature-freeze they could be called Alpha, Beta... It would avoid unnecessary discussion and panicking.. not everyone reads the milestone plan like they ought to :-)
Am Thursday 10 August 2006 15:12 schrieb Silviu Marin-Caea:
On Thursday 10 August 2006 15:27, Marcus Meissner wrote:
On Thu, Aug 10, 2006 at 02:29:36PM +0200, Dominique Leuenberger wrote:
jdd@dodin.org 10-08-2006 14:45 >>>
In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates...
One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome)
I think the latter are already tested by they developpers when the first seems already in a very early stage.
I'm disquieted by the "most annoying bugs" list and the _may be_ delayed Alpha 3.
I personnally think that a stable distribution is better
.than the very most up to date one.
Hi,
I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3).
We have Alpha3. Bugs are expected ;)
Perhaps replacing Alpha with Devel would convey the right message to people, that these releases are development releases that are not feature-complete or in feature-freeze. After feature-freeze they could be called Alpha, Beta...
It would avoid unnecessary discussion and panicking.. not everyone reads the milestone plan like they ought to :-)
What is the difference between Alpha and Devel for you ? Alphas are no feature complete and not feature frozen in mind. -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
On Thu, Aug 10, 2006 at 04:12:30PM +0300, Silviu Marin-Caea wrote:
On Thursday 10 August 2006 15:27, Marcus Meissner wrote:
On Thu, Aug 10, 2006 at 02:29:36PM +0200, Dominique Leuenberger wrote:
jdd@dodin.org 10-08-2006 14:45 >>>
In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates...
One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome)
I think the latter are already tested by they developpers when the first seems already in a very early stage.
I'm disquieted by the "most annoying bugs" list and the _may be_ delayed Alpha 3.
I personnally think that a stable distribution is better
.than the very most up to date one.
Hi,
I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3).
We have Alpha3. Bugs are expected ;)
Perhaps replacing Alpha with Devel would convey the right message to people, that these releases are development releases that are not feature-complete or in feature-freeze. After feature-freeze they could be called Alpha, Beta...
It would avoid unnecessary discussion and panicking.. not everyone reads the milestone plan like they ought to :-)
Lets just call it "Factory". Ciao, Marcus
Silviu Marin-Caea wrote:
On Thursday 10 August 2006 15:27, Marcus Meissner wrote:
On Thu, Aug 10, 2006 at 02:29:36PM +0200, Dominique Leuenberger wrote:
jdd@dodin.org 10-08-2006 14:45 >>> In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates...
One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome)
I think the latter are already tested by they developpers when the first seems already in a very early stage.
I'm disquieted by the "most annoying bugs" list and the _may be_ delayed Alpha 3.
I personnally think that a stable distribution is better .than the very most up to date one.
Hi,
I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3). We have Alpha3. Bugs are expected ;)
Perhaps replacing Alpha with Devel would convey the right message to people, that these releases are development releases that are not feature-complete or in feature-freeze. After feature-freeze they could be called Alpha, Beta...
It would avoid unnecessary discussion and panicking.. not everyone reads the milestone plan like they ought to :-)
Replacing standard mark for development stage Alpha, Beta and RC, with more general "development" will produce panic in more people that will be disoriented in what stage is the project. Only thing that we can do is to point out the definition, that tells: "Alpha is first stage in development, Beta is second, RC, alias Release Candidate, third and last, before Gold Master which is final released version." And of course point to Project Milestones panel on the very Front page. -- Regards, Rajko. Visit http://en.opensuse.org/MiniSUSE
"Dominique Leuenberger"
I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3). The worst that can happen to openSUSE is having (again) a release with bugs like the updater in 10.1. Even though they are fixed now, it's still around and poeple installing without an internet connection most obviosuly run into it.
For me Alphas have a lower quality than Betas have and I they might be broken sometimes in ways that would never be acceptable for a final release.
If the schedule for 10.2 should be kept like this (which I think it should) then we should try to put bugs away instead of adding last-minute-features and packages. Some might be solved with new packages, some might not.
The X11 change was planned for a long time but it was indeed a bit tight at the end. Btw. in general my plan is: * Release AlphaN * Break everything;-) (I mean: put new stuff in that could be broken) * Stabilize again in time for our AlphaNplus (after two weeks) * Stabilize furthr for the next public Alpha Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (6)
-
Adrian Schröter -
Andreas Jaeger -
Dominique Leuenberger -
Marcus Meissner -
Rajko M -
Silviu Marin-Caea