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 <elb...@debian.org> 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
