Re: Renovating debbugs (was Re: Interesting learnings about Guix contributor dynamics that apply to Debian?)

To: Julien Plissonneau Duquène <sre4ever@free.fr>
Cc: debian-devel@lists.debian.org
Subject: Re: Renovating debbugs (was Re: Interesting learnings about Guix contributor dynamics that apply to Debian?)
From: Lucas Nussbaum <lucas@debian.org>
Date: Tue, 27 May 2025 21:59:53 +0200
Message-id: <[🔎] aDYZuX-aFyMVkgE7@grub.nussbaum.fr>
In-reply-to: <[🔎] 6af44c79-1388-f4ff-0cd9-834ec53f8181@free.fr>
References: <[🔎] 6af44c79-1388-f4ff-0cd9-834ec53f8181@free.fr>

On 27/05/25 at 18:46 +0200, Julien Plissonneau Duquène wrote:
> 6. track merge requests.

Maybe something similar to bts-link[0]?
- add a new field that allows pointing to a merge request (similar to
  the 'forwarded' field)
- have a bot that processes bugs with merge requests and adjust BTS tags
  (add 'patch' if the bug has a MR; add 'pending' if the MR has been
  merged)

[0] https://bts-link-team.pages.debian.net/bts-link/

Lucas

Reply to:

References:
- Renovating debbugs (was Re: Interesting learnings about Guix contributor dynamics that apply to Debian?)
  - From: Julien Plissonneau Duquène <sre4ever@free.fr>

Prev by Date: Re: Bug#1106648: ITP: bitcoin-knots -- Bitcoin Knots enhanced Bitcoin node/wallet software
Next by Date: Re: new contributor annoyances (was Re: Interesting learnings about Guix contributor dynamics that apply to Debian?)
Previous by thread: Re: Renovating debbugs (was Re: Interesting learnings about Guix contributor dynamics that apply to Debian?)
Next by thread: Re: Renovating debbugs (was Re: Interesting learnings about Guix contributor dynamics that apply to Debian?)
Index(es):
- Date
- Thread