State of maturity for gcc 2.95.3 and gcc 2.96

[Toon Moene]

Bernd Schmidt wrote:

> On Thu, 12 Oct 2000, David O'Brien wrote:

> > Since 3.0 is still quite some time away, can 2.95.3 finally be released?
> > Some very major bugs have been fixed, but commits have been very cautious
> > to that branch.  I'd almost imagine all that would be needed is to do a
> > checkout and tar it up.

> You'd want to fix at least one new bug introduced in reload...

This would indicate that our process to update the release branch is not
correct.

A week ago I proposed the following on the Steering Committee mailing
list - to which I have seen no reply:

<QUOTE>
Now that our "press release" about "GCC 2.96" is out, and I'm
rereading it, it becomes even more harshly clear that the only
"official" thing we have to offer *short of snapshots* is GCC-2.95.2,
which is close to a year old.

Would it be a solution to have snapshots from the release branch too ?

E.g., we define a release branch; hammer on it until it is "bug-free"
(hah :-) and subsequently have weekly snapshots from _that branch_
called GCC-3.0.n which are our "stable releases".

With the same care that went into adding things to the release branch 
before (only fixes which incur no test suite regressions) this should be
a viable option.

Opinions ?
</QUOTE>

Obviously, we have to think about *how* to discern
snapshots-from-the-release-branch from snapshots-from-the-trunk,
but in principle, the above should be possible.

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://g95.sourceforge.net/ (under construction)