On Tue, 2 Jul 2019 09:21:59 +0200 <to...@tuxteam.de> wrote: > On Mon, Jul 01, 2019 at 11:51:10PM +0200, Matthew Crews wrote: > > On 7/1/19 10:24 AM, Default User wrote: > > > Hi. > > > > > > Easy question, maybe hard to answer . . . > > > > > > Is someone has an existing conventional Unstable setup (nothing > > > exotic in hardware or software), what if any special actions > > > should be taken before, during, or after the impending release of > > > the new Stable? > > > > Be ready for Unstable to become...well, unstable again. > > > > Right now Unstable is mostly frozen due to the imminent release of > > Buster. Shortly (immediately?) after Buster is released, Unstable > > will be unfrozen, and the good 'ol Debian Sid everyone knows and > > loves will be back. > > Officially, only "testing" gets really frozen, but still unstable > might be seen as "slush" during that time. Quoting from [1]: > > 6.5.1 What about "testing"? How is it `frozen'? > > When the "testing" distribution is mature enough, the release > manager starts `freezing' it [...] > > After a while, the "testing" distribution becomes truly `frozen' > [...] > > When a "testing" release becomes `frozen', "unstable" tends > to partially freeze as well. This is because developers are > reluctant to upload radically new software to unstable > > So expect those "reluctant developers" to go a bit wild after > the release :-) >
They haven't exactly been quiet during the freeze. Tens of megabytes a day on my workstation, often over 100. But yes, major architecture changes tend to be kept in the pipeline until after release. -- Joe
