[cut-team] Daily wheezy snapshot installation media now available

[Michael Gilbert]

On Tue, 8 Feb 2011 12:22:24 +0000 Adnan Hodzic wrote:

> > I'm now running a cronjob to create daily wheezy snapshot installation
> > media.  The the media will be available at [0], and snapshots for the
> > last couple days are already up there.  Note that this is highly
> > automated, I've only spot checked one of the images to make sure it
> > fully succeeds through an installation.
> 
> *thumbs up
> 
> > This really isn't a user-oriented solution, so at some point there will
> > need to be a discussion on selection criteria to determine which media
> > should be available for general consumption.
> 
> My general idea for determining media was after "big" things have been
> rolled into testing, for example new kernel, udev, or even new
> Chromium version for that matter. After that kind of things, "cut"
> would be made.

Hi, I was thinking more of a mostly schedule-based process (with of
course flexibility for when things are really broken). That way users
can plan around a upgrading to the new CUT say once a month on about the
same day every month.

> > My thought was to
> > simply use the first image from the month (after a couple days of
> > testing to make sure its in pretty good shape), but I'm of course open
> > to other perspectives.
> 
> I'm not sure if you tried to say the same thing, but I would make it
> available for general public after ~<= month "cut" has been made, and
> has been tested.
> 
> Testing time of the "cut" should be measure by how many "cuts" do you
> want until the "final" release.

OK, here's my plan, and I'm very open to thoughts on improvements.  The
first CUT release candidate will be the first image of every month.
There will be a call for testing to -devel, and if no significant
showstoppers are reported to this list by the 5th day of the month,
then that will be the official release for the month.

If there is a showstopper, the previous images will be bisected and
tested until the one before that problem was present. That will then be
release candidate 2.  There will be a call for another 5 days of
testing, and if no show stoppers are found, then that will be the
official release for the month.

This can be done multiple times, and if we get all the way back to the
previous month's image, then we'll just skip the release for that
month since it's just too buggy.

I'm going to plan to do this for March.

Best wishes,
Mike