As I recall, the release of XFree86 4.0 made it just under the wire for the 7.1 code
freeze. You will find terms not used in a standard manner here. For example, the
"beta" of development is just frozen code--nothing new to be added, but it does NOT
mean that all the in-house discoverable bugs have been found. Some beta-testers have
been bitterly critical about that but it was just the most appropriate term to use
which approximately paralleled a radically different development model. Snapshot is
snapshot--not nightly build, and it means that there was not adequate time before the
code freeze to do anything to the release--so the debugging was short. If you decide
to hang around, the terms will take on new meanings or perhaps you will invent some
terms for the folks to use which describes the development system and its aspects and
products.
Civileme
Sean Middleditch wrote:
> Anton Graham wrote:
>
> > Submitted 10-Jul-00 by Sean Middleditch:
> >
> > > How trustworthy are these RPM's?
> > >
> > > For example, the install on MDK 7.1 said the Xfree86 4.0 is was installing was
> > > only a 'snapshot release.' The really upsets me if it is, because it sure as
> > > hell wasn't advertised as being so... If not, then that's just another
> > > example of MDK's poor quality control when it comes to installations.
> >
> > Have you visited www.xfree86.org? XF4 is not ready for primetime
> > according to them, which is why every other distro oly offers XF3.
> > While many of us, myself included, are able to run it with no
> > difficulty, it is experimental sofware, part of being on Mandrake's
> > "bleeding edge," not poor quality control.
> >
>
> A snapshot release of XF86 4.0 and the fact that 4.0 isn't ready for prime-time are
> two different things altogether... a snapshot would mean either a) based off of
> code before 4.0 was released, which would be unstable, or b) code after 4.0 but
> before 4.01, in between releases, which would be unstable. Bleeding edge would be
> a non-snapshot of 4.0. Perhaps they simply mis-used the work snapshot, but it
> worried me none-the-less.
>
> Sean Middleditch
