What makes a new cooker? Some days I update and it's 25 megs. Today, after a
few days wait, it was 330 megs. Maybe a better approach would be to wait as a
user a week between updates...I am sure that as the daily changes are made,
the people working on the packages appreciate the feedback and would prefer
not to have to wait a whole week.
My $.02 (US)
--
On Thursday 31 May 2001 17:57, you wrote:
> If the cooker releases were reduced to just 1 or 2 a week, then the
> Mandrakesoft staff would actually have time to test, before releasing a
> cooker to ensure the minimal functionality of installing, and booting.
>
> I just think that a majority of problems that weren't addressed in the 8.0
> release came because of the philosohy of the gaurenteed daily releases. 24
> hours isn't enough time for people to do a good job until the next release.
>
> ---- On Wed, 30 May 2001, Tim ([EMAIL PROTECTED]) wrote:
> > This idea has one flaw that I forsee as a fatal one. What if that one
> > release is a complete dud? There have been times in the past when a
> > cooker
> > release was a complete no go for some people. They needed the daily
> > updates
> > to get back to testing. Perhaps personally you could just upgrade files
> > from
> > time to time and then do a complete install once a week for testing
> > purposes? Personally I like my hourly cron job running the rsync script
> > to
> > update my local tree.
> >
> > Just my 2 cents.
> >
> > -Tim
> >
> > > And a weekly cooker doesn't mean a featureless one. We can throw all
> >
> > the
> > new,
> >
> > > bleeding and hemorrhaging edge technology we want into the weeks
> >
> > cooker,
> > and
> >
> > > spend the week not only addressing the regular components, but also
> >
> > the
> > new-
> >
> > > technology ones.
> > >
> > > If a weekly cooker sounds too sparse, how about two weekly cookers?
> >
> > One
> > at the
> >
> > > beginning of the week, one at the end?
> > >
> > > Just thought this might be a good idea.
