Old bug reports

[Charlie Kravetz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 24 Aug 2011 19:01:23 +0100
Carl Ansell <afccarl1994 at hotmail.com> wrote:

> 
> Thanks for the replies.
> 
> 
> I saw a bug report earlier that was marked as confirmed in Dapper, and fix released or invalid (can't remember which)in Edgy and there was a comment stating the issue was fixed in this release. The fix has not been backported, so what would be the best practice in this situation?
> 
> 
> In realise that looking at old bugs might not seem like the most productive thing to do, but I have only just joined the bugsquad and feel that I am still learning about the whole bug reporting and triaging process. As such I think this would be a more simple thing to start with, given that many bugs have been inactive for years and would be less of an issue should I make a mistake.
> 
> 
> 
> Thanks again,
> Carl

If the bug is fixed in any release, but still present in a release that
is now EOL, you can comment that the release it was reported in is no
longer supported and the bug will not be fixed in that non-supported
release. It can then be closed as invalid for that release.

However, again, I would state that no bug is automatically invalid for
being old. Please verify that the bug is not present in the latest
stable or development release before closing the bug report. 

- -- 
Charlie Kravetz 
Linux Registered User Number 425914          [http://counter.li.org/]
Never let anyone steal your DREAM.           [http://keepingdreams.com]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJOVUGxAAoJEFNEIRz9dxbAZywIAI7upUqOSkI7sYC3l9UWZmi9
jKi+y1O8g8VMun5Khhd/WLD+bQ76SCDbIcHt8eVowSsuEI37tvHRT0HV+HDoQ+CP
uY14OqEf4uod+hvesJXpyU/Ws4aKi8XtmRgovaIdq1QRL00ZjykTwPEwsZGFY9BP
ZTg/gZJXFl1VYP1sOe6HNv1O13wqRJuR/wvBUyRSTKlL1j6JJT7t//QyDRow+XLE
W5QHt6BpXdsZ6ZijUnHtCxvZd3/a4eQY50zfll6CnVeP1Qcxb1Ue774LKqJJMutt
uaIeLr3o3UKAcovEB+7waG1v3i7JeAyu4VTKMBmn3HXbeGjlLE0qUS2Wgxz6XtA=
=lUdV
-----END PGP SIGNATURE-----