[cut-team] Where do we go from here?

Raphael Hertzog hertzog at debian.org
Thu Sep 23 13:04:33 UTC 2010


Hi,

in case you haven't noticed, I published a summary of the discussions
in a LWN article:
http://lwn.net/Articles/406301/
Or this link if you're not subscriber:
http://lwn.net/SubscriberLink/406301/bd522adc828b3461/

A discussion spontaneously started on -devel yesterday[1] a few hours before
the article was published. Thus lucas posted[2] a link to my article in the
thread to solicit comments.

[1] http://lists.debian.org/debian-devel/2010/09/msg00484.html
[2] http://lists.debian.org/debian-devel/2010/09/msg00529.html

While this summary is useful, and while the -devel discussion might
provide new insights, it's time IMO to see who's ready to put work into
this project. And then to reach out to other teams who are impacted. And
then to take decisions.

Are you ready to work on snapshots? If yes, do you have conditions?

Are you ready to work on rolling? If yes, do you have conditions?

My response:

> Are you ready to work on snapshots? If yes, do you have conditions?

I don't plan to work on this. I might help from time to time but I will
not drive this. My personal preference is to have snapshots every 2 to 3
months but feel free to ignore it.

> Are you ready to work on rolling? If yes, do you have conditions?

I am. I can help writing the code to pick updates from testing
into rolling and feed the result to dak. I can help managing
the direct flow of packages that would not go through testing (e.g.
chromium and other packages that we want in rolling that are not
in testing).

I would prefer if rolling's rules were relatively close to testing so that
it can supersede it one day, at which point testing would become a branch
of rolling that starts at freeze time.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693]

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)



More information about the cut-team mailing list