From kde-devel  Wed Sep 24 23:23:42 2008
From: Pino Toscano <toscano.pino () tiscali ! it>
Date: Wed, 24 Sep 2008 23:23:42 +0000
To: kde-devel
Subject: Re: How should the version field in BTS be used?
Message-Id: <200809250123.47763.toscano.pino () tiscali ! it>
X-MARC-Message: https://marc.info/?l=kde-devel&m=122229943004729
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0506451303=="

--===============0506451303==
Content-Type: multipart/signed;
  boundary="nextPart1640924.v9g3TtfU0d";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1640924.v9g3TtfU0d
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

> 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.

No, just most probably leave a comment saying "can(not) reproduce with vers=
ion=20
x.y.z".

> Personally, I think my way makes more sense as it helps to prevent
> bug rot.

Version field usually means "which version was the bug reported against?",=
=20
that turns to developer's "when the bug/regression appeared?", that is a=20
*much* useful information to know.

Keeping the only Version field as "I can reproduce it with this version"=20
completely defeats its point, because there are two possible scenarios:
a) bug can be reproduced -> is open for a reason, then
b) bug cannot be reproduced -> should be closed (after a couple or so relea=
ses=20
when people cannot reproduce it anymore) as either=20
=46IXED/WORKSFORME/INVALID/etc.
and as you can see, none of them really require a version field like that.

=2D-=20
Pino Toscano

--nextPart1640924.v9g3TtfU0d
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBI2sv+TNH2piB/L3oRAiVJAKCDrX1xOq/ta70QWWwTCPmXNEpk/wCfYp3g
yuLU1q5JmchUzfFLn+2LikQ=
=/Fj+
-----END PGP SIGNATURE-----

--nextPart1640924.v9g3TtfU0d--

--===============0506451303==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0506451303==--