Old bug reports
brian at ubuntu.com
Wed Aug 24 19:31:28 UTC 2011
On Wed, Aug 24, 2011 at 12:23:45PM -0600, Charlie Kravetz wrote:
> -----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.
Please also keep in mind that if the bug does not have a specific
release task (like http://launchpad.net/bugs/830923 which you can see
says "Oneiric" in it) the bug is considered to affect the current
development release of Ubuntu. This is even the case if there is
release specific information in the description. We assume that the bug
also exists in the current development release.
Ubuntu Bug Master
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: Digital signature
More information about the Ubuntu-bugsquad