Ac stable on our doorstep?

[Marcin Król]

> "Always in development" is the way for us, but doing this (for TH) needs
> some thought and writing some conception:
> 
>       * define a new way of making 'stable' freezes for ISO (when to
>         freeze)

Each 4 months if there were no big updates like gcc, glibc? Or
immediately after such big upgrades.

>       * come up with a way of planning drastic changes for next stable
>         freeze

The way we currently do that seems quite OK. New stuff (gcc etc.) lands
in devel version and whole devel tree is being prepared for it. When
this new software reaches stable state then after some final
adjustements its moved to stable tree and all dependent packages are
rebuilt.

>       * agree on periodical freezes (once a half year?), or event based
>         (new GNOME/KDE, new gcc etc...), or PLD way - when it's ready ;)

Yes. 4 or 6 month as I mentioned above. Event based would be nice too.
We just have to decide which one will be best for us. Current PLD way is
not an option here or nothing will change.

>       * define an upgrading fashion: we guarantee that one step upgrade
>         is always possible (like freeze 1 upgrade till 2, but not till
>         3,4), which means that having an old iso would need to d/l all
>         further isos and upgrade version by version, or better, find a
>         way of making upgrade possible through many freezes (which
>         implies inventing a way of freezing ensuring this will be always
>         possible)

We don't have dozens of developers so we probably can't guarantee more
than 1 step upgrade.

M.