On Wed, Jan 14, 2026 at 04:05:36PM +0100, Vincent Lefevre wrote:
> On 2026-01-13 20:18:57 -0500, Derek Martin wrote:
> > On Mon, Jan 12, 2026 at 01:30:46PM +0100, Alejandro Colomar via Mutt-dev 
> > wrote:
> > > > As long as these issues are clearly labeled as 'feature request', once
> > > > some devs are running out of work, they can search closed issues for
> > > > unresolved FRs.
> > > 
> > > IMO and IME, closed means resolved.
> > 
> > Sure, but "resolved" does not necessarily imply "implemented."
> > Bugzilla, for example, and actually every bug management system I've
> > worked with, had statuses like "INVALID" or "WONTFIX" and rightly so.
> 
> Actually these are not statuses, but resolution types:

Ugh.  Yes, pedantically speaking using Bugzilla's own terminology,
sure.  But actually, generically speaking, the resolution type is just
part of the overal status of the ticket, in the English sense of the
word, i.e. the common noun "status," not Bugzilla's proper noun
"Status."  Since I explicitly mentioned other bug management systems,
my comments should not have been interpreted to refer specifically to
Bugzilla's terminology.

Sigh.

> In short, the meaning of "resolved", "closed" and so on really
> depends on the bug tracker (not just the software like Bugzilla, but
> particular instances).

Yes; or said another way, it's dependent on how the maintainers want
to use them.  They're the folks saddled with the actual work, so they
generally can, generally should, and generally do, decide how the bug
tracker workflow works.  Not to say the community shouldn't have
input, but the tool should work primarily for those who are the
primary users of it, i.e. the maintainers.

For the sake of pedantry, by "maintainers" I mean, "those who 
predominantly shoulder the burden of triaging, debugging, fixing, and
updating issues in the bug tracker, and releasing new versions with
those fixes" (distinct from those who only occasionally or never do
those things, who, myself certainly included, would be more accurately
described as "contributors").

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.

Reply via email to