[cut-team] Ideas for the rolling release

[Lucas Nussbaum]

On 17/08/10 at 10:21 +0200, Reinhard Tartler wrote:
> On Tue, Aug 17, 2010 at 09:27:38 (CEST), Lucas Nussbaum wrote:
> 
> > On 16/08/10 at 22:00 -0400, Joey Hess wrote:
> >> OTOH, going from 3 to 4 really ramps up the combinatorial complexity of
> >> interactions/propigation between suites to possibly brain-melting
> >> levels.
> >
> > I think that it depends on the definition of rolling. If it's defined as:
> > - testing + a few manually hinted packages in non-freeze times
> > - same migration scheme as testing in freeze times
> > Then it doesn't seem so complex to me.
> 
> From a practical POV, it requires users to reconfigure their
> sources.list if they want to stick with the 'promised' update policy.
> 
> This is probably not that complex to explain, but surprising and
> requires users to actively watch out.

That could be handled by the installer.

- Lucas