On Sun, 30 Oct 2005, Mark Mitchell wrote: > Until now, when I've decided something is not important enough to > require fixing for a particular release, I unset the target milestone. > That's confusing because it might seem to mean that I'm saying the bug > *can't* be fixed for a particular release, which isn't true. > > So, I'm going to adopt a new convention in these cases. In particular, > I'm going to leave the target milestone alone, but set the priority field.
Does this mean regressions for languages and platforms other than those in the release criteria should now have the milestone set, but be marked as P4 or P5? -- Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ [EMAIL PROTECTED] (personal mail) [EMAIL PROTECTED] (CodeSourcery mail) [EMAIL PROTECTED] (Bugzilla assignments and CCs)
