This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: bugs fixed in 3.0.3 -- second draft
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Cc: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, Joe Buck <jbuck at synopsys dot com>, <gcc at gcc dot gnu dot org>
- Date: Fri, 21 Dec 2001 22:05:37 +0000 (GMT)
- Subject: Re: bugs fixed in 3.0.3 -- second draft
On Fri, 21 Dec 2001, Neil Booth wrote:
> I agree - if you (or someone else) create an HTML template to list bug
> fixes in, we should get committers to add their fixes to it under the
> relevant category. It won't take much additional time. Having it in
> HTML on the web pages also means users can see real-time bug-fix
> status during development, without having to wait for a release
> announcement.
>
> We should do something similar for 3.1 starting now IMO. Do you
> agree?
A third suggestion for gathering the information - rather than supposing
that people know all the PR numbers fixed by a current or past commit, and
rather than trying to identify for individual bugs which version they were
fixed in, provide a standard way of specifying relevant PRs in testcases,
then extract a list of PRs by running regression tests with the current
testsuite against the future and past releases.
The release notes for 3.1 - including the features list, etc. - certainly
ought to start now. (Actually, we should start the 3.2 notes as soon as
3.1 branches, so people can add each new feature to the release notes as
and when they add that feature. As is, we can start by backfilling the
features list from the news items from the web pages, as was done for
3.0.)
--
Joseph S. Myers
jsm28@cam.ac.uk