Should patches for PR target/1532 go on 3.4 branch?

[Giovanni Bajo]

Ian Lance Taylor wrote:

> OK, bugmasters, what should happen now to PR target/1532?  It is
> targeted at 3.4.0.  It has now been fixed for 3.4.0.  The 3.3 branch
> is still open.  It is a regression for the 3.3 branch.

Then, your job is to retarget it to 3.3.4, and then let the RM (Gaby) decide. I
see that Andrew took care of moving the milestone, so it's ok as is. Gaby can
either:

- Keep it open, hoping someone will fix it somehow on 3.3 or backport the
patch.
- Close it as fixed, moving the target milestone back to 3.4.0 (as "first
version in which the bug is fixed"), specifying that a fix for the 3.3 branch
is impossible / unwanted.

> Perhaps the fact that the target has been set to 3.4.0 means that it
> has already been decided that this PR will not be fixed in the 3.3
> branch, and therefore we can close it now?  That would make sense to
> me.

You can check in the activity log. Mark moved it to 3.4.0 before releaseing
3.3.2 (because it was supposed to be the last 3.3 release). Then we simply
forgot to move the milestone back to 3.3.3 when Gaby took over the branch.

Giovanni Bajo