On 22 Sep 2000, Guillaume Cottenceau wrote:
> "Sergio P.Korlowsky" <[EMAIL PROTECTED]> writes:
>
>
> [...]
>
> > > Beta number 3 !
>
> [...]
>
> > Well.... definetly I give up...!!!!
> >
> > After several atempts to stay up to date with the latest beta,
> > always get new packages when I think am done downloading.
> >
> > I do not have a fast connection to the net, I depend on a 56kbps modem...
> > so I most definetly HAVE to wait untill it 'trully' freezes 'completely'
> > to be able to cach up with the beta release.
>
> Yep -- basically we are currently in the process of proposing one Beta as
> ISO image per week. Soon it will be some Release Candidates.
>
>
> > If at lest it would stop for a few hours the constant upgrading of packages...
> > I would be able to finish downloading. (I am talking about 7.2 beta)
> > ;-)
>
> Try now. It's the week-end now and we will be far less people to upload
> new packages.
>
> > not cooker.... (cooker I know and I understand is constantly changing) but
> > 7.2 is supposed to be frozen (?) untill a new beta is release... am I wrong?
>
> Yes but we are currently constantly fixing new bugs as long as they are
> discovered!
>
>
>
Ok, I appreciate the need to fix bugs. How about doing daily freezes? At
least this way I know I am installing a complete build, and can then
update the new files manually. As it stands, everytime I want to do a
clean install, there are new files to download. Wouldn't be a problem if I
wasn't worried that something is being uploaded as we speak needed by some
of these files I'm getting now which I may miss if I don't run rsync
again.
Having betas and cooker going on at the same time seems silly to
me. Frozen betas and an ongoing cooker seem to make the most sense to
me. Then again, I'm no expert.
JP
