Thijs Kinkhorst <th...@debian.org> schrieb: > On Thu, December 29, 2011 09:10, Adam D. Barratt wrote: >> On 28.12.2011 23:45, John Wright wrote: >>> Attached is a patch to the python-debian package which I intend to >>> upload to stable. >> >> Apparently you already _have_ uploaded it. >> >> Eight hours is really not a long enough time to have waited for a >> response, particularly when practically all of the release team memebers >> handling stable are in Europe and were likely asleep for the majority of >> those eight hours. For future reference, the expected workflow - as >> outlined in the Developers Reference and a number of mails to d-d-a - is >> to wait for an acknowledgement before uploading. Now that you've >> uploaded the package will be processed in due course, but it would be >> appreciated if you could bear this in mind for any future uploads. > > This problem seems to occur with regular intervals. Wouldn't it be > possible to change dak so that uploads are queued in a way that makes it > less of a problem should they not be accepted lateron? Also makes it > easier for the uploader (upload it now - don't have to keep your build > around) and the srm's (can review the actual uploaded package instead of > an emailed debdiff). Perhaps something like a DELAYED queue with infinite > delay?
Or simply add a "really upload" confirmation as it's already done for security uploads: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458628 (At least for dput, we really should converge to a single archive upload helper... ) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjfolt0.5mh....@inutil.org
