On Fri, Aug 20, 2021 at 11:01:08AM +0200, Stephan Lachnit wrote: > > Problem: Currently uploading new upstream versions to unstable during freeze is discouraged. It means users using unstable don't get new updates and developers are forced to upload to experimental. Using experimental directly is risky as it can have changes not ready for unstable also. > > Proposed solution: open unstable-proposed-updates with freeze and close it when freeze is lifted. The packages in this suite can migrate to testing, this avoids manual reuploads to unstable after freeze is lifted. > > Optional: create a companion testing suite say rolling which may be used during this time and a second Britney instance can manage migration to this suite. > > I agree that the situation with experimental during the freeze is a > problem. I think it makes more sense to do a testing-proposed-updates > instead of an unstable-proposed-updates suite, as that more closely > reflects what's actually happening. If you mean keeping unstable as is and uploading stuff for testing into t-p-u, that's was always called a bad idea, as nobody tests stuff in t-p-u. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature