[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: How should the version field in BTS be used?
From:       Michael Leupold <lemma () confuego ! org>
Date:       2008-09-24 23:07:51
Message-ID: 200809250107.51804.lemma () confuego ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 25 September 2008, Richard Hartmann wrote:
> I was under the impression that when you are able to reproduce a bug
> in a newer version, you should, if possible, bump the version of the
> component it was filed against.
> As a few of my changes have just been reverted, I wanted to check
> if I am correct or mistaken.
> Personally, I think my way makes more sense as it helps to prevent
> bug rot. On the other hand, I do not want to go against established
> procedures, either.

As far as I know, different components handle it differently. From bugsquad's 
point of view it would make sense to make the semantics the same for all of 
them - this would make it easier for us and other developers to understand 
what's going on.

We do however understand that different developers/teams have different ways 
of handling the version field and we respect that. I do hope that the new 
Bugzilla (and custom fields) could help this situation by making the version 
field say the same KDE-wide and introducing/using extra-fields to express the 
different semantics needed by different products.

Bugsquad's preferred meaning of the version field:
- for open bugs: The version this bug was last tested/reproduced on
- for closed bugs: The last version this bug could be reproduced on

Other possible meanings of the version field:
- target release
- the version this bug was reported on

No objection to picking another meaning as "default" - still having it the 
same would be nice.

Regards,
Michael

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]