[opensuse-factory] Critical RC2 bug: quitting quadrapassel kills x-server
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too? Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper? Thanks -- Atri -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag 02 Juli 2010 schrieb Atri Bhattacharya:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
A ship stopper at this point basically means: it's impossible to fix with an online update and is so severe that many people will notice it. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 02 July 2010 14:16:32 Atri Bhattacharya wrote:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
This kind of bug could be fixed with an online update, so I would not call it a shipstopper. Still if the fix looks good, I'm sure Coolo will evaluate for taking it into the final build. I see as shipstopper the following but let's ask Coolo what he thinks: * a serious data loss or security problem right after start that we could not easily fix wiht an update. * anything in the update stack or installation that would not let you install the system completely and update to fix the problem Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 02/07/10 22:32, Andreas Jaeger wrote:
On Friday 02 July 2010 14:16:32 Atri Bhattacharya wrote:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
This kind of bug could be fixed with an online update, so I would not call it a shipstopper. Still if the fix looks good, I'm sure Coolo will evaluate for taking it into the final build.
I see as shipstopper the following but let's ask Coolo what he thinks: * a serious data loss or security problem right after start that we could not easily fix wiht an update. * anything in the update stack or installation that would not let you install the system completely and update to fix the problem
Andreas
But "Coolo" just wrote, A ship stopper at this point basically means: it's impossible to fix with an online update and is so severe that many people will notice it. Greetings, Stephan So then, what is the true situation now? BC -- Fact is that which enough people believe. Truth is determined by how fervently they believe it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Jul 02, 2010 at 10:43:05PM +1000, Basil Chupin wrote:
On 02/07/10 22:32, Andreas Jaeger wrote:
On Friday 02 July 2010 14:16:32 Atri Bhattacharya wrote:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
This kind of bug could be fixed with an online update, so I would not call it a shipstopper. Still if the fix looks good, I'm sure Coolo will evaluate for taking it into the final build.
I see as shipstopper the following but let's ask Coolo what he thinks: * a serious data loss or security problem right after start that we could not easily fix wiht an update. * anything in the update stack or installation that would not let you install the system completely and update to fix the problem
Andreas
But "Coolo" just wrote,
A ship stopper at this point basically means: it's impossible to fix with an online update and is so severe that many people will notice it.
Greetings, Stephan
So then, what is the true situation now?
What the release manager writes, he is the final arbiter. And "Coolo" is this release manager ;) Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/07/10 22:44, Marcus Meissner wrote:
On Fri, Jul 02, 2010 at 10:43:05PM +1000, Basil Chupin wrote:
On 02/07/10 22:32, Andreas Jaeger wrote:
On Friday 02 July 2010 14:16:32 Atri Bhattacharya wrote:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
This kind of bug could be fixed with an online update, so I would not call it a shipstopper. Still if the fix looks good, I'm sure Coolo will evaluate for taking it into the final build.
I see as shipstopper the following but let's ask Coolo what he thinks: * a serious data loss or security problem right after start that we could not easily fix wiht an update. * anything in the update stack or installation that would not let you install the system completely and update to fix the problem
Andreas
But "Coolo" just wrote,
A ship stopper at this point basically means: it's impossible to fix with an online update and is so severe that many people will notice it.
Greetings, Stephan
So then, what is the true situation now?
What the release manager writes, he is the final arbiter.
And "Coolo" is this release manager ;)
Ciao, Marcus
Aaah, thanks Marcus. All clear to me now. 'The Program Manager openSUSE' has no real say or control in any of this. Understood old chap. BC -- Fact is that which enough people believe. Truth is determined by how fervently they believe it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 02 July 2010 14:43:05 Basil Chupin wrote:
On 02/07/10 22:32, Andreas Jaeger wrote:
On Friday 02 July 2010 14:16:32 Atri Bhattacharya wrote:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
This kind of bug could be fixed with an online update, so I would not call it a shipstopper. Still if the fix looks good, I'm sure Coolo will evaluate for taking it into the final build.
I see as shipstopper the following but let's ask Coolo what he thinks: * a serious data loss or security problem right after start that we could not easily fix wiht an update. * anything in the update stack or installation that would not let you install the system completely and update to fix the problem
Andreas
But "Coolo" just wrote,
Coolo was faster in sending his answer and I did not see his mail before I send mine.
A ship stopper at this point basically means: it's impossible to fix with an online update and is so severe that many people will notice it.
Which seems to be a variation of my two points. We do not disagree, he just added the part "many people". And if in doubt: Coolo is the release manager ;) Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 02/07/10 22:51, Andreas Jaeger wrote:
On Friday 02 July 2010 14:43:05 Basil Chupin wrote:
On 02/07/10 22:32, Andreas Jaeger wrote:
On Friday 02 July 2010 14:16:32 Atri Bhattacharya wrote:
Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too?
Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper?
This kind of bug could be fixed with an online update, so I would not call it a shipstopper. Still if the fix looks good, I'm sure Coolo will evaluate for taking it into the final build.
I see as shipstopper the following but let's ask Coolo what he thinks: * a serious data loss or security problem right after start that we could not easily fix wiht an update. * anything in the update stack or installation that would not let you install the system completely and update to fix the problem
Andreas
But "Coolo" just wrote,
Coolo was faster in sending his answer and I did not see his mail before I send mine.
A ship stopper at this point basically means: it's impossible to fix with an online update and is so severe that many people will notice it.
Which seems to be a variation of my two points. We do not disagree, he just added the part "many people". And if in doubt: Coolo is the release manager ;)
Andreas
And Marcus's response, and mine to him, beat your response :-) . I'll make no further comment.... BC -- Fact is that which enough people believe. Truth is determined by how fervently they believe it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Andreas Jaeger -
Atri Bhattacharya -
Basil Chupin -
Marcus Meissner -
Stephan Kulow