This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bugzilla update and schedule for changeover
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Phil Edwards <phil at jaj dot com>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, <gcc at gcc dot gnu dot org>
- Date: Sat, 22 Mar 2003 09:15:38 +0000 (GMT)
- Subject: Re: Bugzilla update and schedule for changeover
On Fri, 21 Mar 2003, Phil Edwards wrote:
> IMHO, it'd be better to do the changeover ASAP, so we can start getting
As soon as we have the doc patch for the manual and the web pages (the
usual requirement for docs for changes). (The web page patch will need to
patch releasing.html and branching.html to explain the need to teach
Bugzilla about the new mainline version number (when branching) (e.g.
3.5) or the new point version number (when releasing) (e.g. 3.3.1), so
that the version number pulldown includes the new number and the email
converter properly handles full version numbers including the new number,
as well as the need to add new milestones for the same version numbers,
and deal with open bugs still set to the milestone for the release just
made.)
[The doc patch also needs to cover
* queryhelp.cgi, whose list of bug statuses doesn't include the customised
ones for GCC. [Could configuration and scripts like this go in CVS?]
[Could UNCONFIRMED and SUSPENDED be included in the statuses of bugs
selected by default in the query form?]
* By association, gcc_release, which at present includes gnats.html and a
plain text version thereof in release tarballs and may need to include
other files in future.
* sourcebuild.texi which has a checklist of what is needed when adding a
front end - at present including a new GNATS category.
All patches to the source tree rather than web pages CVS should go on 3.2
and 3.3 branches as well as mainline.]
--
Joseph S. Myers
jsm28 at cam dot ac dot uk