[Cooker] Cooker - when is it 'safe' to use again . . .

[Robert Fox]

Great work on 2010 - I see Cooker is reopened - is it safe to use
immediately?  Or should we wait a bit?

I was waiting for KDE 4.3.3 and the new NVidia drivers

Also, it would be nice if we continue the tradition of advanced warnings
when Cooker is temporarily broken (like major packages being updated or
rebuilt) - this lets us Cooker users know when to "proceed with caution"

All the best moving forward . . .

Robert Fox

On Saturday 07 of November 2009 20:36:40 Robert Fox wrote:
> Great work on 2010 - I see Cooker is reopened - is it safe to use
> immediately?  Or should we wait a bit?
>

yesterday plasma crashed, today I get desktop again :)

> I was waiting for KDE 4.3.3

You will get 4.4 beta.

> and the new NVidia drivers
>

Are there.

> Also, it would be nice if we continue the tradition of advanced
>  warnings when Cooker is temporarily broken (like major packages
>  being updated or rebuilt) - this lets us Cooker users know when to
>  "proceed with caution"
>

KDE is in process of updating from 4.3 to 4.4. Go figure :)

[Frederik Himpe]

On za, 2009-11-07 at 18:36 +0100, Robert Fox wrote:
> Great work on 2010 - I see Cooker is reopened - is it safe to use
> immediately?  Or should we wait a bit?

Cooker is by definition never safe. Don't run it on mission critical
systems, because things can get broken any time.

> I was waiting for KDE 4.3.3 and the new NVidia drivers

We are switching to KDE 4.4 development snapshots... New Nvidia drivers
are available in 2010.0 backports AFAIK.

--
Frederik Himpe <fhimpe@...>

[Robert Fox]

On Sat, 2009-11-07 at 18:49 +0100, Frederik Himpe wrote:
> On za, 2009-11-07 at 18:36 +0100, Robert Fox wrote:
> > Great work on 2010 - I see Cooker is reopened - is it safe to use
> > immediately?  Or should we wait a bit?
>
> Cooker is by definition never safe. Don't run it on mission critical
> systems, because things can get broken any time.
>
I agree and accept this - the question is, when a 'major' update is
underway (like the KDE from 4.3.2 to 4.4 devel snapshots) it would be
nice to know when it is considered complete enough to start testing.
Just like you did with the Gnome updates (an advanced warning on Cooker
mailing list stating that for the next day or two Gnome may be seriously
broken until all the updates are pushed out.

I have found Cooker to be quite stable despite its 'bleeding edge' feel
- and all I ask it that when something major is being implemented, that
it be announced in advance.

The package maintainers do some preliminary testing before they get on
Cooker - right?

> > I was waiting for KDE 4.3.3 and the new NVidia drivers
>
> We are switching to KDE 4.4 development snapshots... New Nvidia drivers
> are available in 2010.0 backports AFAIK.
>

Thanks for the tip - I am awaiting my wonderful prize (Powerpack 2010
download) for the background picture I submitted in the contest :-)

All the best -
Robert

[Frederik Himpe]

On za, 2009-11-07 at 19:10 +0100, Robert Fox wrote:

> The package maintainers do some preliminary testing before they get on
> Cooker - right?

Definitely no. It's quite exceptional that a package was first tested by
the maintainer, before it is submitted to cooker.

--
Frederik Himpe <fhimpe@...>

[Christophe Fergeau-3]

Robert Fox a écrit :
> I have found Cooker to be quite stable despite its 'bleeding edge' feel
> - and all I ask it that when something major is being implemented, that
> it be announced in advance.
>  

Minor updates can also totally break things, so I'm not sure this brings
much to announce "major" changes in advance :)

Christophe

[Robert Fox]

On Thu, 2009-11-12 at 15:12 +0100, Christophe Fergeau wrote:

> Robert Fox a écrit :
> > I have found Cooker to be quite stable despite its 'bleeding edge' feel
> > - and all I ask it that when something major is being implemented, that
> > it be announced in advance.
> >  
>
> Minor updates can also totally break things, so I'm not sure this brings
> much to announce "major" changes in advance :)
>
> Christophe

Agreed - but what I mean is like the entire rebuild of KDE for QT 4.6 -
this a major and we have to wait for all pieces in place before we
should submit bugs against it.

Cheers,
Robert

[Christophe Fergeau-3]

Robert Fox a écrit :
>
> Agreed - but what I mean is like the entire rebuild of KDE for QT 4.6 -
> this a major and we have to wait for all pieces in place before we
> should submit bugs against it.
>  

Well, in this case, the rebuild happened because a seemingly minor and
harmless qt update broke all of KDE and thus triggered the rebuild. So
it was not really possible to warn people in advance :)

Christophe

[JMiahMan]

I have always been under the impression that Cooker is never really safe to use. I thought that was the point of it, when it is safe normally that's when a release comes. Until then you live dangerously running it. You take risks with every update, for my it's the adrenaline rush of the next update that keeps me going. :) When it is broke (like yesterday) I think oh crap I hope the next update fixes this, but I don't complain or even post because thus is the life of the cooker tester, excitement and danger..

[Toni Diaz]

2009/11/12 Jeremiah Summers <jmiahman@...>

I have always been under the impression that Cooker is never really safe to use. I thought that was the point of it, when it is safe normally that's when a release comes. Until then you live dangerously running it. You take risks with every update, for my it's the adrenaline rush of the next update that keeps me going. :) When it is broke (like yesterday) I think oh crap I hope the next update fixes this, but I don't complain or even post because thus is the life of the cooker tester, excitement and danger..

+1.
The wiki explains it clearly: is a dangerous way of life...