When you say distro, what are you referring to besides the apps?? Isn't a "distro" just a particular conglomeration of different OSS apps chosen on their suitability for use by end users?? I realize that there are other additions ie. installer, config tools, software managers etc. provided by the distro in question but in comparison, that is only a small part of the total code in any major distro's release.

Look, I've been a "cooker" for quite a while now so I understand what you are saying but I hope you see my point as well. I won't waste any more list time on this topic. /end/rant.

Cheers

Jason

Ben Reser wrote:
On Wed, Nov 27, 2002 at 12:57:44PM +1300, Jason Greenwood wrote:
  
Wouldn't it pay to make an exception when the one on the App providers 
mirror is MORE stable (though it may be a beta) than the one that is in 
Cooker?? Just a thought...

Besides, can't the testing/problems/bugfixes that Cooker users can 
provide be of use to Mozilla.org anyway?? We test betas of MANY programs 
in cooker anyway, why should Mozilla be any different? Isn't the whole 
point of cooker to be "bleeding edge"?? We are a great testbed due to 
the deep level of technical knowlege brought to the table by many of the 
cookers.
    

We're here to test the distro.  Not the apps.  The applications have
betas etc for their own testing purposes.  The few pre-release versions
that get put into cooker are put there for one of several reasons:

a) Mandrake developer works on the product. (KDE)
b) Mandrake makes specific changes from the shipped version. (KDE,
Gnome).
c) To fix bugs that it isn't possible to patch and that won't have a
release to fix them prior to shipping.  Generally these are critical
bugs, i.e. the app isn't working right at all.

Considering that Mozilla is pretty close to the 1.2 release I don't
think there's much benefit in packaging it right now.

  

Reply via email to