Future of Ac... or even of PLD

Bartosz Świątek shadzik w gmail.com
Czw, 22 Mar 2007, 18:00:35 CET


2007/3/22, Cezary Krzyzanowski <dhubleizh w o2.pl>:
> Dnia 22-03-2007, czw o godzinie 14:33 +0100, Marcin Król napisał(a):
>
> > Th probably will not get stable enough in next 2-3 months to replace
> > production systems, so here we are back with idea of "always in
> > developement" way for PLD. It was discussed few times so I'll post just
> > some basic information: two trees, one marked as stable, second as
> > devel. Things from devel that will be stable enough are moved to stable
> > tree. From time to time or after some big changes a new snapshot is
> > being released for all those .iso images fans. Third tree may be
> > introduced for completly unstable stuff like gcc snapshots etc.
> >
> > I will at least try such way of developement for Ac. That means some big
> > changes for Ac 2.1. First of all, clean upgrade from 2.0 probably will
> > not be possible. By clean upgrade I mean 'poldek --upgrade-dist' going
> > w/o errors.
> >
>
> IMHO doing always in current should be a decision for the whole PLD, not
> just AC. It's strange to first make AC the stable branch of PLD - the
> one we release and just after it make it 'the new thing' with
> always-current model. Th is fresh, is in development state and I see no
> need to make AC as well in development state especially with a totally
> new release/development cycle.
>
> If we are to make a big change in our distros lifecycle let's make it in
> th. I already has all the things You want to get into AC and has more
> human-power to make the transition possible in sane time.

Isn't it strange that people who don't even commit to AC-branch have
the most to say in this topic ? And please, to everyone, keep this
topic consistent, I'm really pissed off when I get answers to it in
different threads.


Więcej informacji o liście dyskusyjnej pld-discuss