Hello,
On Tue 15 Jul 2025 at 07:43pm +01, Simon McVittie wrote:
> On Tue, 15 Jul 2025 at 15:18:08 +0100, Sean Whitton wrote:
>>It's not about speed, but about being able to set the bug aside.
>
> Yes, I was agreeing with you - like I said, grouping together all the work
> into one "transaction" h
On Tue, 15 Jul 2025 at 15:18:08 +0100, Sean Whitton wrote:
It's not about speed, but about being able to set the bug aside.
Yes, I was agreeing with you - like I said, grouping together all the
work into one "transaction" has value, and DELAYED enables that.
On Tue 15 Jul 2025 at 02:33pm +0
On Tue, Jul 15, 2025 at 06:16:40PM +0200, Lucas Nussbaum wrote:
> I think that Otto and Sean are discussing the merits of DELAYED vs MR vs
> bugs for NMU-like contributions, while you are discussing how this
> particular contribution (improving doc) should be handled.
ah, lol, thanks Lucas. Pleas
On 15/07/25 at 15:57 +, Holger Levsen wrote:
> On Tue, Jul 15, 2025 at 11:43:01AM +0100, Sean Whitton wrote:
> > Yeah, me too (though I'd prefer a BTS bug to an MR, but it's the same).
>
> I definitly prefer an MR for such a change.
>
> (For more controversial changes I prefer to have a BTS t
On Tue, Jul 15, 2025 at 11:43:01AM +0100, Sean Whitton wrote:
> Yeah, me too (though I'd prefer a BTS bug to an MR, but it's the same).
I definitly prefer an MR for such a change.
(For more controversial changes I prefer to have a BTS track record, because
salsa can go away, while the BTS will st
On 15/07/25 at 12:03 +0200, Otto Kekäläinen wrote:
> +1 to clarifying the DELAYED queue section. Please also include an
> example dcut command on how to remove a package from the DELAYED queue
> if the maintainer does not want to have it.
Right
> Personally I would much rather see a contribution
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
On Tue 15 Jul 2025 at 12:03pm +02, Otto Kekäläinen wrote:
If I am
completely missing, I would be fine if somebody posted a MR and then
after a few weeks went and merged it themselves and uploaded. This
would still feel more collaborative than noticing a new package
version as NMU in DELAYED. Does
Hello,
On Tue 15 Jul 2025 at 12:03pm +02, Otto Kekäläinen wrote:
> +1 to clarifying the DELAYED queue section. Please also include an
> example dcut command on how to remove a package from the DELAYED queue
> if the maintainer does not want to have it.
>
> Personally I would much rather see a con
+1 to clarifying the DELAYED queue section. Please also include an
example dcut command on how to remove a package from the DELAYED queue
if the maintainer does not want to have it.
Personally I would much rather see a contribution being submitted to
my packages as a Merge Request on Salsa, than a
Package: developers-reference
Version: 13.20
Severity: wishlist
X-Debbugs-Cc: ti...@debian.org
Hi,
The delayed/deferred queue mechanism is documented in section 5.6.3
(Delayed uploads). However
https://lists.debian.org/debian-devel-announce/2008/09/msg6.html has
more details about queue handl
11 matches
Mail list logo
