This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

gcc 2.98 release better approach?


Hi,
    I wanted to just make a suggestion. Given that a rather
large vendor has stirred the pot on this by releasing a cvs
version of gcc perhaps a change in plan might help. Rather
than going straight to gcc 3.0 without official releases
wouldn't it make more sense to branch a 2.98 release just
before the v3.0 libstdc++ was switched on in the gcc cvs?
That would help folks on Redhat by providing some place
to go for a more stable release than they have now while
allowing the v3.0 libstdc++ to destablize the cvs branch.
I think such an approach helps everyone involved since
a real 2.98 release with all the code changes except
v3.0 libstdc++ would provide a huge pool of beta testers
to fix bugs which could be immediately migrated into
the main cvs. Likewise changes to the main cvs that don't
totally destabilize code generation could go back into
the 2.98 release branch. Such an approach would seem to
meet everyone half way. Keeping Redhat users from getting
hung out to dry while giving gcc some very nice real world
testing of the newer code from gcc cvs.
                         Jack Howarth

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]