[cut-team] snapshot frequency

[Joey Hess]

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.
> 
> By "major update" I mean, something where release notes are useful.
> For security updates, you can use unattended-upgrades, for stable
> point releases you maybe do it by hand, but still don't worry; but
> after a month's development of testing, there's good odds something
> significant has changed that might require some human intervention
> (even if it's just monitoring config file changes).

Aren't we targeting people who *want* a rolling release though?

We should make the upgrades as painless as possible, and sure, document
when there are problems.

-- 
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/cut-team/attachments/20100910/21760cbb/attachment.pgp>