Em Tue, 28 May 2002 09:19:26 -0500, Steve Langasek <[EMAIL PROTECTED]>
escreveu:
> No, tagging the bug 'potato' only means that it's a bug that pertains
> specifically to potato. There are NO RC bugs that are potato-specific,
> because potato is already released. ;) And for security-related bug
On Tue, May 28, 2002 at 07:54:14PM +1000, Matthew Palmer wrote:
> But a bug marked 'potato' but that won't be fixed because it's not security
> critical - is that still a bug? I mean, it is an issue with the package,
> but because it only affects potato (or, by extension, the stable
> distributi
On Tue, May 28, 2002 at 01:12:38AM -0700, Sean 'Shaleh' Perry wrote:
> setting it to Potato shows that it has either been fixed or obsoleted in more
> recent versions.
Though the more common thing is just to close the bug unless it's
frequently reported.
--
"You grabbed my hand and we fell int
On Tue, 28 May 2002, Sean 'Shaleh' Perry wrote:
> > And what about when, for instance, potato is replaced as the stable distro
> > by Woody? Should the bug be closed then because it's no longer relevant?
> > Perhaps it's closed automatically because it's tagged 'Potato', I don't
> > know.
> >
>
> And what about when, for instance, potato is replaced as the stable distro
> by Woody? Should the bug be closed then because it's no longer relevant?
> Perhaps it's closed automatically because it's tagged 'Potato', I don't
> know.
>
> Anyway, just trying to think my way through a few issu
When a bug applies to an old version of a package (say, a version only in
Potato) when should that bug be closed? If it's not security or
life-threatening to the package, it will pretty much never get fixed in
Potato, but it's still a bug. Perhaps it should be tagged wontfix and be
done with it?
6 matches
Mail list logo
