[cut-team] snapshot frequency

[Anthony Towns]

On Sat, Sep 11, 2010 at 04:53, Joey Hess <joeyh at debian.org> wrote:
> Anthony Towns wrote:
>> My concern is that it'd mean (as a user) you'd have to worry about
>> major functionality changes fairly frequently. Assuming 2 year stable
>> cycles:
>>  - 1 month CUT cycle = 1-23 updates before hitting stable
>>  - 3 month CUT cycle = 1-7 updates before hitting stable
>>  - 6 month CUT cycle = 1-3 updates before hitting stable
>> For me, dealing with 7 major updates (including the final switch to
>> the next stable release) sounds feasible, 23 sounds really annoying.
> Aren't we targeting people who *want* a rolling release though?

It's certainly /a/ target. It's not really the one that interests me though.

I'm interested in:

 * being able to do a "testing-ish" install on a system to get newer
hardware support or newer features than stable has, while not needing
to pay it too much more attention than a stable install would need (so
few/infrequent functionality changes, decent security support).
Obviously it'll need *some* more attention, but 3x or 7x over two
years seems way more plausible than 20x. (For the latter, I can
already use testing and just upgrade irregularly. It's not really
satisfactory, but it works)

 * having newer/more stuff available for testing/unstable-type users
without making the release team's job harder.

Cheers,
aj

-- 
Anthony Towns <aj at erisian.com.au>