Non-stable releases of several pieces of software are
regularly released. the non stability of these
releases can be due to many things ... such as code
being broken, or libraries not completely implemented.
There are reasons why one SHOULD bring out new
versions.After all, one may not KNOW completely why
that particular relase is broken, or mangled in some
other way that was not thought of before. I agree that
RedHat made a gross error in releasing the new
unstable release of gcc (one of the more important
tools in linux development and administration) and
labelling it wrongly, but then, it is precisely these
releases that produces corrections (sometimes
brilliant solutions) to unknown problems.
rajeev j sebastian
--- Raghavendra Bhat <[EMAIL PROTECTED]> wrote:
> Hello: Red Hat users' migrating to Red Hat v7.0 are
>
> warned of severe incompatibilities. Please read the
> below given link:
>
>
http://gcc.gnu.org/ml/gcc-announce/2000/msg00003.html
>
> This shows that release cycles have to be brought
> down.
> There is no point is bringing out NEW versions if it
> is
> going to be totally broken and incompatible.
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/
----------------------------------------------
LIH is all for free speech. But it was created
for a purpose. Violations of the rules of
this list will result in stern action.
