On Thu, Jan 06, 2011 at 10:31:28PM -0800, Ian Lance Taylor wrote:
> > 2. A large number of bugs seem to not be targetted for any particular
> > release, e.g. of the 4389 open bugs, only 296 are listed as targetted
> > for 4.6.0. Why is there such a discrepency?
> >
> > Incidentally, my main focus will be on these untargetted bugs rather
> > than on bugs that are already scheduled to be fixed.
>
> For an open bug, a target of 4.6.0 means only that the bug is known to
> fail on current mainline. It doesn't mean that the bug is more likely
> to be fixed for 4.6.0 than any other current bug. At least, as far as I
> know; the release managers or bugmasters may have a better idea.
target field is mainly used for tracking the regressions (the canned queries
from gcc.gnu.org homepage). For a regression (with [4.x/4.y/4.z Regression]
in the subject) it should be set to the next patchlevel version of the gcc
release in which we'd like it to be fixed, if it is decided that it won't be
fixed say in 4.4 because the fix is too invasive there, target will be changed
to 4.5.3 etc.
> > 3. If I mark a bug as known to fail in 4.5.2, will someone else then
> > schedule it to be fixed in 4.6.0?
>
> No. People choose bugs to work on based mainly on the priority and on
> whether the bug is a regression or not. As far as I know people do not
> look at the target field.
The queries do though.
Jakub
