[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Closing bugs in experimental (was #1114180)



On Mon, Sep 08, 2025 at 12:34:54PM +0200, Santiago Vila wrote:
> Paul Gevers wrote:
> > > So: I have to call those who advocate for marking bugs fixed in
> > > experimental as "closed" in the BTS and I invite you to answer the
> > > following simple question: Where in earth is stated that version
> > > tracking *mandates* such thing?
> > 
> > The default behavior of our archive is that if you add a "Closes: #bug" to
> > your changelog, that the bug is closed. I consider that "documentation by
> > code" and long standing tradition.
> 
> That's just a default. Such default is useful because most of the time
> you only want to fix the bug in a single distribution, usually
> unstable.
> 
> If we are going to use the "tradition" argument, it's also a long
> standing tradition to change things when their default values do not
> suit our needs.

As someone firmly in the "version tracking is BTS's killer feature"
camp, I am convinced by the above. By salsa analogy, uploading to
experimental is comparable to the commit hook to tag the bug as
"pending".

experimental is special, since it's outside our automatic suite
migrations. I also suspect it has become much more used than it was pre
2010 as release processes have become more strict, binNEW adjustments,
so maybe it's time to tweak it to DTRT.

I don't think it's worth the effort to change any individual maintainer
behaviour one way or the other like this thread started with.
--
emorrp1

Attachment: signature.asc
Description: PGP signature


Reply to: