Bug#855811: release.debian.org: release.d.o WWW should explicitly recommend against uploading to sid during the freeze
Hello, On Thu 14 Mar 2019 at 07:48PM +01, Paul Gevers wrote: > I the attached patch what you are looking for? Yes, thank you, although I would wordsmith it as follows (take it or leave it as you like): ... it is recommended that, during the freeze, you do not upload to unstable any changes for which you do not intend to request an unblock. -- Sean Whitton signature.asc Description: PGP signature
Bug#855811: release.debian.org: release.d.o WWW should explicitly recommend against uploading to sid during the freeze
Hi Sean, On 08-03-2019 02:12, Sean Whitton wrote: > No, I don't think so. You have to think moderately hard to infer, "oh, > stop uploading to sid" from that text. I would suggest appending > "I.e. only upload to sid changes for which you plan to request an unblock." I the attached patch what you are looking for? Paul From 6bd6b8f8c8120e01084715429e09cd657c22fe8b Mon Sep 17 00:00:00 2001 From: Paul Gevers Date: Thu, 14 Mar 2019 19:45:02 +0100 Subject: [PATCH] freeze_policy.md add recommendation to not upload to unstable during the freeze Closes: #855811 --- www/buster/freeze_policy.md | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/www/buster/freeze_policy.md b/www/buster/freeze_policy.md index 0e2e9fc..2e6fb72 100644 --- a/www/buster/freeze_policy.md +++ b/www/buster/freeze_policy.md @@ -203,7 +203,10 @@ point. We strongly prefer changes that can be done via unstable instead of testing-proposed-updates. If there are unrelated changes in unstable, you should consider reverting these instead of making an upload to -testing-proposed-updates. +testing-proposed-updates. Hence, and also because it may impact other packages +in unstable that try to migrate to buster, it is recommended to not upload +changes to unstable in this period that you don't intent to request an unblock +for. Applying for an unblock -- 2.20.1 signature.asc Description: OpenPGP digital signature
Bug#855811: release.debian.org: release.d.o WWW should explicitly recommend against uploading to sid during the freeze
Hello Paul, On Thu 07 Mar 2019 at 09:37PM +01, Paul Gevers wrote: > On Tue, 21 Feb 2017 15:04:39 -0700 Sean Whitton > wrote: >> I'd like to suggest that this recommendation be stated explicitly on the >> release team's website, to reduce the number of blocking uploads to >> unstable made during the freeze. > > Is the current text good enough for this purpose? > """ > We strongly prefer changes that can be done via unstable instead of > testing-proposed-updates. If there are unrelated changes in unstable, > you should consider reverting these instead of making an upload to > testing-proposed-updates. > """ No, I don't think so. You have to think moderately hard to infer, "oh, stop uploading to sid" from that text. I would suggest appending "I.e. only upload to sid changes for which you plan to request an unblock." -- Sean Whitton signature.asc Description: PGP signature
Bug#855811: release.debian.org: release.d.o WWW should explicitly recommend against uploading to sid during the freeze
Hi Sean, Sorry it took so long to get a reply. On Tue, 21 Feb 2017 15:04:39 -0700 Sean Whitton wrote: > I'd like to suggest that this recommendation be stated explicitly on the > release team's website, to reduce the number of blocking uploads to > unstable made during the freeze. Is the current text good enough for this purpose? """ We strongly prefer changes that can be done via unstable instead of testing-proposed-updates. If there are unrelated changes in unstable, you should consider reverting these instead of making an upload to testing-proposed-updates. """ Paul signature.asc Description: OpenPGP digital signature
Bug#855811: release.debian.org: release.d.o WWW should explicitly recommend against uploading to sid during the freeze
Package: release.debian.org Severity: wishlist Dear release team, release.d.o WWW says If you are unable to bring your fix through unstable, for example because there are unrelated changes already uploaded there, the release team can grant you permission to use the testing-proposed-updates mechanism. It is possible to infer from this that one should not upload anything to unstable unless it is a targeted fix for a bug in testing. However, one might not make this inference before making an upload of, say, a new upstream version. DDs make this mistake from time-to-time. In my own case, I was only aware of the release team's recommendation to use experimental because I watched the release team's presentation at debconf17. So far as I can tell, this recommendation is not documented anywhere, nor stated in any recent editions of "Bits from the Release Team". I'd like to suggest that this recommendation be stated explicitly on the release team's website, to reduce the number of blocking uploads to unstable made during the freeze. Thanks! -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Sean Whitton signature.asc Description: PGP signature
