long term support release

[Stephen John Smoogen]

On Jan 26, 2008 8:48 PM, Krzysztof Halasa <khc at pm.waw.pl> wrote:
> Till Maas <opensource at till.name> writes:
>
> > Afaik, there are sometimes changes that cannot be done within the running
> > system.
>
> They could be done next boot.
>

Not always... there have been several changes that could only be done
via a chroot environment. If for example ext4 were to be chosen for
Fedora XII it would need a chroot. Large changes in how glibc work are
probably better examples..

> > Also the new releases are useful whenever an update of a package
> > requires manual intervention, because then this can be documented in the
> > release notes and then there are no unpleasent surprises.
>
> If a package knows a manual intervention is needed it could postpone the
> upgrade. Release notes could be updated as needed.
>
> > And the update
> > cycles also allow to be sure that some update-paths do not need to be
> > supported anymore, e.g. when a conversion of a config file is needed and the
> > latest release with the old config file is old enough, the code within the
> > spec can be skipped.
>
> Continuous update doesn't mean ability to update from arbitrarily old
> package versions, the "supported" period could be shorter than
> now. You would have to be able to update from the last bootstrap disc,
> that's all.
>
> --
> Krzysztof Halasa
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>



-- 
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"