The question of rolling release?

[Kevin Kofler]

mike cloaked wrote:
> That way once installed there is no need to maintain and test updates
> specifically for the current release.  As an overall workload would
> this actually be any more effort than the constant stream of testing
> for the "two" current releases - as an overall picture?

Of course it's less work for us if we only do Rawhide, but then that leaves 
our users with nothing usable for production machines at all!

This is a no go.

Any rolling model which is suitable for production machines would be 
completely unsupportable, because it'd mean you'd have to be able to 
individually opt out of every single migration, leading to an exponential, 
and thus both untestable and unmaintainable, explosion of possible setups.

There is just no alternative to doing releases for the disruptive changes.

        Kevin Kofler