IMO - By the time that the bug is resolved I think it should reflect the
actual version it was fixed in. If there is a hot bug though (like a
major issue), sometimes its cool to signify that something needs to be
done about it by the next major release because then it's clear how many
open issues need to get fixed before we release.
So the way I see it, we could go one of two ways:
1. Allow people to set the fixby if they think an issue is important and
then, at some point, put the ownis on the person performing the release
to review the outstanding bugs and mark them as "unscheduled" if they
are not important or
2. To not let the filer set the fixby and instead have it be set by the
person who is actually fixing the bug.
I personally think #2 fits the Apache process better and if a bug is
particularly debilitating, the filer can either fix it himself or
encourage someone else in the community (via the mailing lists) to fix
it for them.
Scott
Andrew Robinson wrote:
I am seeing more and more users setting the fix release as a way to
put down when they seem to want to have it fixed by. It was my
understanding that this should only be used to mark what release the
actual fix has been placed in. If so, is there a way that we can put
security around the fix version so that only the person that the bug
is assigned to can set this field?
-Andrew
