On Jo, 21 oct 21, 13:00:09, Sam Hartman wrote:
> Simon> However, the problem with freezing testing but not freezing
> Simon> unstable is that if you do that, all updates to testing
> Simon> during the freeze (to fix the release-critical bugs that stop
> Simon> it from already being
Simon> However, the problem with freezing testing but not freezing
Simon> unstable is that if you do that, all updates to testing
Simon> during the freeze (to fix the release-critical bugs that stop
Simon> it from already being ready for release) have to go into
Simon> testing
Thomas Goirand dijo [Wed, Oct 20, 2021 at 10:51:59PM +0200]:
> >> That's obviously what I'm doing. But when there's 2 releases during the
> >> freeze, it means one of them will never reach Unstable.
> >
> > Right, which makes perfect sense.
> (...)
> > I guess very few will, but if it's needed,
On 2021-10-21 02:24:19 +0200 (+0200), Thomas Goirand wrote:
[...]
> What I don't know is how far OpenStack went for supporting
> skipping releases. For example, would it work to upgrade from
> Rocky (in Buster) to Victoria (in Bullseye) directly? For which
> projects?
I don't think so, at least
On 10/21/21 12:29 AM, Jeremy Stanley wrote:
> On 2021-10-20 22:51:59 +0200 (+0200), Thomas Goirand wrote:
> [...]
>> In most OpenStack projects, you cannot skip an OpenStack release,
>> at least because of the db schema upgrades.
> [...]
>
> Upstream, I want to keep pushing on what we referred to
On 2021-10-20 22:51:59 +0200 (+0200), Thomas Goirand wrote:
[...]
> In most OpenStack projects, you cannot skip an OpenStack release,
> at least because of the db schema upgrades.
[...]
Upstream, I want to keep pushing on what we referred to as
"skip-level upgrades" which would be something akin
On Wed, Oct 20, 2021 at 10:51:59PM +0200, Thomas Goirand wrote:
> On 10/20/21 7:50 PM, Gunnar Wolf wrote:
> > Thomas Goirand dijo [Wed, Oct 20, 2021 at 09:11:13AM +0200]:
> >>> You can upload it to experimental
> >>
> >> That's obviously what I'm doing. But when there's 2 releases during the
> >>
On 10/20/21 7:50 PM, Gunnar Wolf wrote:
> Thomas Goirand dijo [Wed, Oct 20, 2021 at 09:11:13AM +0200]:
>>> You can upload it to experimental
>>
>> That's obviously what I'm doing. But when there's 2 releases during the
>> freeze, it means one of them will never reach Unstable.
>
> Right, which
Thomas Goirand dijo [Wed, Oct 20, 2021 at 09:11:13AM +0200]:
> > You can upload it to experimental
>
> That's obviously what I'm doing. But when there's 2 releases during the
> freeze, it means one of them will never reach Unstable.
Right, which makes perfect sense.
The group of people
On 10/20/21 7:52 AM, Andrey Rahmatullin wrote:
> On Wed, Oct 20, 2021 at 02:43:47AM +0200, Thomas Goirand wrote:
>>> However, the problem with freezing testing but not freezing unstable is
>>> that if you do that, all updates to testing during the freeze (to fix the
>>> release-critical bugs that
On 10/20/21 6:47 AM, Mechtilde Stehmann wrote:
> Hello,
>
>
> Am 20.10.21 um 02:43 schrieb Thomas Goirand:
>> Hi Simon,
>>
>> For me, the long freeze are very problematic. They may spawn for 6
>> months, which is how long it takes for a new OpenStack release to show
>> up, and then I don't know
On Wed, Oct 20, 2021 at 02:43:47AM +0200, Thomas Goirand wrote:
> > However, the problem with freezing testing but not freezing unstable is
> > that if you do that, all updates to testing during the freeze (to fix the
> > release-critical bugs that stop it from already being ready for release)
> >
Hello,
Am 20.10.21 um 02:43 schrieb Thomas Goirand:
> Hi Simon,
>
> For me, the long freeze are very problematic. They may spawn for 6
> months, which is how long it takes for a new OpenStack release to show
> up, and then I don't know where to upload it... :/
You can upload it to experimental
Hi Simon,
For me, the long freeze are very problematic. They may spawn for 6
months, which is how long it takes for a new OpenStack release to show
up, and then I don't know where to upload it... :/
As a result, the Wallaby release of OpenStack (released last spring)
never had the time to
>
> https://wiki.debian.org/ReleaseProposals
>
Great list, contains a lot of what I have to say.
The fact that debian is laser focused on stable, and does not officially
encourage using testing as a rolling release (as evidenced from a couple
replies to this email chain), yet there are still
On Mon, 18 Oct 2021 at 12:29:55 -0400, Peter Hoist wrote:
> So the question is, why not cut a release branch every two years, and at the
> same time keep the unstable/testing alive?
We have this conversation about once a year. Essentially, the freeze makes
sure that the versions we are proposing
Hi,
I am enjoying Debian's testing branch as a reasonably stable and up-to-date
'rolling' release, and I have to say it satisfies all my desires, almost.
The one thing that bothers me is that every two years, the unstable/testing
branches are frozen to certain extent because of the stable
17 matches
Mail list logo
