Bug#671066: ftp.debian.org: upload urgencies should not accumulate
On Tue, 1 May 2012, Philipp Kern wrote:
> > > However, if urgencies accumulate, how are we supposed to really mean
> > > "10 days" after an upload not of low priority? It's impossible!
>
> No. The idea is that if you specify urgency=medium that *this* *change* (not
> upload!) should go into testing in an expedited fashion.
Well, I understand the "idea", but the idea still seems wrong to me.
It is not the "changes" the ones that go to testing, it's the
upload the one that goes to testing.
Accordingly, the urgency is put on the upload, not on the "changes".
There is not a way to put an urgency on the changes other than putting
an urgency on the upload.
When I put an urgency on an upload, I put it on that upload, not on
the upload and "all the uploads that come next".
> If you then go and upload something else in the meantime that's
> your problem, as we still want the change in testing.
You speak "we" as if you were excluding the maintainer from such "we".
Please consider the possibility that "we" the maintainers still
want our urgencies to be honored!
> You could a) wait for the previous version to hit testing
> or b) ask the release team to override the urgency of your most recent upload.
>
> The only case where urgencies should not accumulate is if you take a different
> branch and upload it without the changes in the previous version.
And here you speak "the only case" as if it were a rare exception.
How do you know that the upload is not trying to fix the same thing in
a better way¿ Answer: You don't.
For that reason, the assumption that the upload is "on the same
branch" is gratuitous. It could be the case, but it could be not the
case as well.
Reply to: