Hi Olivier, > I see some uploads to unstable during the freeze. I understood it was > not expected as fixes that need to go to "next stable" go through > uploads to unstable. > > While this should not be an issue for packages that do not present > issues at this time, I'd like to know if we should anyway push to unstable ?
just my 2 cents, but I've done it like this so far: - If there is a new version of a package which is not in testing (e.g. entered unstable after the NEW freeze) then I upload straight to unstable as there's no need to stay close to the frozen testing for fixes. - If there's a frozen version in testing, I open a new 'next' or 'experimental' branch in git with the new version and upload it to experimental. Since experimental is separate, once the freeze is over it should just be a matter of rebuilding and re-uploading the new version to unstable. - If a package is completely NEW, then it's fine to upload directly to unstable since there's no way it will affect the frozen stretch. Any comments or suggestions from the others? I didn't to this out of habit for ariba (uploading to unstable) and of course now there's an (upstream related) RC bug for the stretch version with a newer version in unstable :/ This would have been more of a routine if unstable would have been clean... Cheers Sascha
