Hi
When I go through RC bugs I see more and more bugs which are both found
and fixed with the same version.
This does NOT work: these bugs are treated as if they are not fixed at all.
Please do not version bug closures when there were no changes to the
source package to get the bug fixed!
Note
On Sun, Aug 15, 2010 at 04:25:19PM +0200, Luk Claes wrote:
When I go through RC bugs I see more and more bugs which are both found
and fixed with the same version.
This does NOT work: these bugs are treated as if they are not fixed at all.
Why not change the way they are treated? You can
On 08/15/2010 04:41 PM, Guus Sliepen wrote:
On Sun, Aug 15, 2010 at 04:25:19PM +0200, Luk Claes wrote:
When I go through RC bugs I see more and more bugs which are both found
and fixed with the same version.
This does NOT work: these bugs are treated as if they are not fixed at all.
Why
On Sun, Aug 15, 2010 at 04:57:40PM +0200, Luk Claes wrote:
Why not change the way they are treated? You can easily use the date a
message is sent to bugs.debian.org to see if it comes before or after other
messages closing/opening the bug tagged with the same version.
Because it is sane
On 08/15/2010 06:17 PM, Guus Sliepen wrote:
On Sun, Aug 15, 2010 at 04:57:40PM +0200, Luk Claes wrote:
It's very strange that you think it's ok to mark a bug as fixed in a
specific version even if there was nothing changed in the package to get
the bug fixed IMHO.
Well, if, like in your
On Sun, 15 Aug 2010, Guus Sliepen wrote:
I think that if people are actively opening and closing bugs (in
that order) with the same Version tag, they expect the bug to be
closed. I also do not think that there is any danger in having it
marked as closed, it can always be reopened later.
The
6 matches
Mail list logo
