This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Need target milestone 3.3.2
- From: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, <gcc-patches at gcc dot gnu dot org>, <dberlin at dberlin dot org>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Tue, 3 Jun 2003 11:38:12 -0500 (CDT)
- Subject: Re: Need target milestone 3.3.2
> Yes, that would be great! It's in wwwdocs/htdocs/releasing.html. If
Ah, that already explains how to do it. So 3.3.2 now exists :-)
> someone will put instructions that say how to create the milestone, I
> will take care of it during the release cycle. It might also make sense
> to put a similar note in branching.html.
Like so?
W.
Index: branching.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/branching.html,v
retrieving revision 1.12
diff -c -r1.12 branching.html
*** branching.html 25 Mar 2003 01:14:18 -0000 1.12
--- branching.html 3 Jun 2003 16:36:16 -0000
***************
*** 72,77 ****
--- 72,81 ----
choosing gcc, and editing the milestones. Please do <strong>not</strong>
delete old target milestones.</li>
+ <li>Create new target milestones in Bugzilla for the second dot
+ release on the branch. For example, when branching 3.4, create a
+ milestone for 3.4.1 for PRs that can't be fixed in time for 3.4.0.</li>
+
<li>Update the email parsing script to handle bugs against the new versions.
The script is in CVS at <code>wwwdocs/bugzilla/contrib/bug_email.pl</code>.
Search for an existing version (like "3.3"), and update both places
Index: releasing.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.14
diff -c -r1.14 releasing.html
*** releasing.html 4 May 2003 11:06:04 -0000 1.14
--- releasing.html 3 Jun 2003 16:36:16 -0000
***************
*** 79,91 ****
and editing the versions. Please do <strong>not</strong> delete old
versions.</li>
! <li>Create a new target milestone in Bugzilla corresponding to the new
! branch version. This can be accomplished by choosing products,
! choosing gcc, and editing the target milestones. Please do
! <strong>not</strong> delete old target milestones.</li>
<li>Change all open bugs targeted at the just released milestone to be targeted
! at either the mainline version milestone, or the point-release milestone.
This can be accomplished by querying for all bugs targeted at the old
milestone, choosing "Change several bugs at once" at the bottom of the
buglist screen, choosing "check all" to select all bugs to change,
--- 79,93 ----
and editing the versions. Please do <strong>not</strong> delete old
versions.</li>
! <li>Create a new target milestone in Bugzilla corresponding to the dot
! release after the immediate next (for example create a milestone for
! 3.3.3 after releasing 3.3.1, so we can slip the milestone for PRs that
! can't be fixed in time for 3.3.2). This can be accomplished by
! choosing products, choosing gcc, and editing the target milestones.
! Please do <strong>not</strong> delete old target milestones.</li>
<li>Change all open bugs targeted at the just released milestone to be targeted
! at either the mainline version milestone, or the next point-release milestone.
This can be accomplished by querying for all bugs targeted at the old
milestone, choosing "Change several bugs at once" at the bottom of the
buglist screen, choosing "check all" to select all bugs to change,