Hello, On Tue 15 Jul 2025 at 02:33pm +01, Simon McVittie wrote: > On Tue, 15 Jul 2025 at 11:43:01 +0100, Sean Whitton wrote: >>The thing about DELAYED is that it's fire-and-forget for the contributor >>actually doing the work, which is an advantage. > > I agree that when the contributor doing the work can only spend a limited > amount of time and attention on it, there is value in grouping together all of > the work to be done the same day (make the change, send to BTS, send MR if > desired, upload to DELAYED) so that in the absence of any other action being > taken, the proposed fix will reach the archive without the contributor needing > to actively herd it through the process. I'm not sure that I see a situation > where it would be rational to use DELAYED, but unacceptably slow to open BTS > bugs or MRs? It's not about speed, but about being able to set the bug aside. I.e., the "forget" is the key word. I track everything meticulously in Org-mode tasks but many volunteers are keen not to have personal to-do lists for work done in their free time. Fire-and-forget enables that. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature