Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Leandro Cunha wrote on 15/03/2022 at 23:18:37+0100: > Hi, > > On Tue, Mar 15, 2022 at 7:05 PM Pierre-Elliott Bécue wrote: >> >> >> Leandro Cunha wrote on 15/03/2022 at >> 22:57:39+0100: >> >> > On Tue, Mar 15, 2022 at 5:16 PM Pierre-Elliott Bécue >> > wrote: >> > >> > Paul Gevers wrote on 14/03/2022 at 21:43:38+0100: >> > >> > > Dear all, >> > > >> > > We are currently considering the following dates as our freeze >> > > dates. If you are aware of major clashes of these dates with anything >> > > we depend on please let us know. We also like to stress again that we >> > > really would like to have a short Hard and Full Freeze (counting in >> > > weeks, rather than months), so please plan accordingly. If serious >> > > delays turn up during any of the Freeze steps, we rather (partially or >> > > completely) thaw bookworm again than staying frozen for a long time. >> > > >> > > 2023-01-12 - Milestone 1 - Transition and toolchain freeze >> > > 2023-02-12 - Milestone 2 - Soft Freeze >> > > 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and >> > > packages without autopkgtests >> > > To be announced - Milestone 4 - Full Freeze >> > > >> > > On behalf of the Release Team, >> > >> > Hi, >> > >> > OOC, isn't that a bit "too short"? We started to work again in August >> > 2021, it'll be less than two years until the freeze. >> > >> > Less than 1 year to go to milestone 1 starts in January. >> >> I was referring to the delay between the end of the freeze and the next >> hard freeze. > > Ok. Debian has been releasing versions every 2 years for a long time. > I was looking at the site here to remember the dates. > It is a cycle that is being continued. > > https://www.debian.org/releases/ I always have been under the impression it was around 2.5 years between releases, but indeed, this impression was false. Thanks! -- PEB signature.asc Description: PGP signature
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Sorry, the follow-up mails loaded only after I wrote my response. Regards Stephan
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Did you mean 2023? Regards Stephan
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Hi, On Tue, Mar 15, 2022 at 7:05 PM Pierre-Elliott Bécue wrote: > > > Leandro Cunha wrote on 15/03/2022 at > 22:57:39+0100: > > > On Tue, Mar 15, 2022 at 5:16 PM Pierre-Elliott Bécue > > wrote: > > > > Paul Gevers wrote on 14/03/2022 at 21:43:38+0100: > > > > > Dear all, > > > > > > We are currently considering the following dates as our freeze > > > dates. If you are aware of major clashes of these dates with anything > > > we depend on please let us know. We also like to stress again that we > > > really would like to have a short Hard and Full Freeze (counting in > > > weeks, rather than months), so please plan accordingly. If serious > > > delays turn up during any of the Freeze steps, we rather (partially or > > > completely) thaw bookworm again than staying frozen for a long time. > > > > > > 2023-01-12 - Milestone 1 - Transition and toolchain freeze > > > 2023-02-12 - Milestone 2 - Soft Freeze > > > 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and > > > packages without autopkgtests > > > To be announced - Milestone 4 - Full Freeze > > > > > > On behalf of the Release Team, > > > > Hi, > > > > OOC, isn't that a bit "too short"? We started to work again in August > > 2021, it'll be less than two years until the freeze. > > > > Less than 1 year to go to milestone 1 starts in January. > > I was referring to the delay between the end of the freeze and the next > hard freeze. > > -- > PEB Ok. Debian has been releasing versions every 2 years for a long time. I was looking at the site here to remember the dates. It is a cycle that is being continued. https://www.debian.org/releases/ -- Cheers, Leandro Cunha Software Engineer and Debian Contributor
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Leandro Cunha wrote on 15/03/2022 at 22:57:39+0100: > On Tue, Mar 15, 2022 at 5:16 PM Pierre-Elliott Bécue wrote: > > Paul Gevers wrote on 14/03/2022 at 21:43:38+0100: > > > Dear all, > > > > We are currently considering the following dates as our freeze > > dates. If you are aware of major clashes of these dates with anything > > we depend on please let us know. We also like to stress again that we > > really would like to have a short Hard and Full Freeze (counting in > > weeks, rather than months), so please plan accordingly. If serious > > delays turn up during any of the Freeze steps, we rather (partially or > > completely) thaw bookworm again than staying frozen for a long time. > > > > 2023-01-12 - Milestone 1 - Transition and toolchain freeze > > 2023-02-12 - Milestone 2 - Soft Freeze > > 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and > > packages without autopkgtests > > To be announced - Milestone 4 - Full Freeze > > > > On behalf of the Release Team, > > Hi, > > OOC, isn't that a bit "too short"? We started to work again in August > 2021, it'll be less than two years until the freeze. > > Less than 1 year to go to milestone 1 starts in January. I was referring to the delay between the end of the freeze and the next hard freeze. -- PEB signature.asc Description: PGP signature
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
On Tue, Mar 15, 2022 at 5:16 PM Pierre-Elliott Bécue wrote: > > Paul Gevers wrote on 14/03/2022 at 21:43:38+0100: > > > Dear all, > > > > We are currently considering the following dates as our freeze > > dates. If you are aware of major clashes of these dates with anything > > we depend on please let us know. We also like to stress again that we > > really would like to have a short Hard and Full Freeze (counting in > > weeks, rather than months), so please plan accordingly. If serious > > delays turn up during any of the Freeze steps, we rather (partially or > > completely) thaw bookworm again than staying frozen for a long time. > > > > 2023-01-12 - Milestone 1 - Transition and toolchain freeze > > 2023-02-12 - Milestone 2 - Soft Freeze > > 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and > > packages without autopkgtests > > To be announced - Milestone 4 - Full Freeze > > > > On behalf of the Release Team, > > Hi, > > OOC, isn't that a bit "too short"? We started to work again in August > 2021, it'll be less than two years until the freeze. > > Less than 1 year to go to milestone 1 starts in January. -- Cheers, Leandro Cunha Software Engineer and Debian Contributor
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Paul Gevers wrote on 14/03/2022 at 21:43:38+0100: > Dear all, > > We are currently considering the following dates as our freeze > dates. If you are aware of major clashes of these dates with anything > we depend on please let us know. We also like to stress again that we > really would like to have a short Hard and Full Freeze (counting in > weeks, rather than months), so please plan accordingly. If serious > delays turn up during any of the Freeze steps, we rather (partially or > completely) thaw bookworm again than staying frozen for a long time. > > 2023-01-12 - Milestone 1 - Transition and toolchain freeze > 2023-02-12 - Milestone 2 - Soft Freeze > 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and > packages without autopkgtests > To be announced - Milestone 4 - Full Freeze > > On behalf of the Release Team, Hi, OOC, isn't that a bit "too short"? We started to work again in August 2021, it'll be less than two years until the freeze. I'm fine with that, but I wonder if we shouldn't keep with a bit larger timelines. Cheers! -- PEB signature.asc Description: PGP signature
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Am Montag, 14. März 2022, 21:36:11 CET schrieb Paul Gevers: > 2022-01-12 - Milestone 1 - Transition and toolchain freeze > 2022-02-12 - Milestone 2 - Soft Freeze > 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and > packages without autopkgtests That's already done? Or in Decembre, in three days? Or, most likely, 2023? Stay safe, Eike signature.asc Description: This is a digitally signed message part.
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Hi Paul, On Mo 14 Mär 2022 21:36:11 CET, Paul Gevers wrote: Dear all, We are currently considering the following dates as our freeze dates. If you are aware of major clashes of these dates with anything we depend on please let us know. We also like to stress again that we really would like to have a short Hard and Full Freeze (counting in weeks, rather than months), so please plan accordingly. If serious delays turn up during any of the Freeze steps, we rather (partially or completely) thaw bookworm again than staying frozen for a long time. 2022-01-12 - Milestone 1 - Transition and toolchain freeze 2022-02-12 - Milestone 2 - Soft Freeze 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and packages without autopkgtests To be announced - Milestone 4 - Full Freeze On behalf of the Release Team, Paul These dates look wrong by one year... (or are we already in Milestone 3 phase now???). Shock in the morning... Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpDteM5leRQu.pgp Description: Digitale PGP-Signatur
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
On Mon, Mar 14, 2022 at 09:43:15PM +0100, Jérémy Lal wrote: > > We are currently considering the following dates as our freeze > > dates. If you are aware of major clashes of these dates with anything > > we depend on please let us know. We also like to stress again that we > > really would like to have a short Hard and Full Freeze (counting in > > weeks, rather than months), so please plan accordingly. If serious > > delays turn up during any of the Freeze steps, we rather (partially or > > completely) thaw bookworm again than staying frozen for a long time. > > > > 2022-01-12 - Milestone 1 - Transition and toolchain freeze > > 2022-02-12 - Milestone 2 - Soft Freeze > > 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and > > packages without autopkgtests > > To be announced - Milestone 4 - Full Freeze > Is it possible to adopt ISO8601 dates like -MM-DD please (to avoid > heart attacks) ? Do you think these phases are so short that they are 1 day each? :) -- WBR, wRAR signature.asc Description: PGP signature
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Hi, On Mon, Mar 14, 2022 at 6:23 PM Jameson Graef Rollins wrote: > > On Mon, Mar 14 2022, Paul Gevers wrote: > > We are currently considering the following dates as our freeze > > dates. If you are aware of major clashes of these dates with anything > > we depend on please let us know. We also like to stress again that we > > really would like to have a short Hard and Full Freeze (counting in > > weeks, rather than months), so please plan accordingly. If serious > > delays turn up during any of the Freeze steps, we rather (partially or > > completely) thaw bookworm again than staying frozen for a long time. > > > > 2022-01-12 - Milestone 1 - Transition and toolchain freeze > > 2022-02-12 - Milestone 2 - Soft Freeze > > 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and > > packages without autopkgtests > > To be announced - Milestone 4 - Full Freeze > > Have not all of these dates already past? Or are these milestones over > three consecutive days in December of this year? > > jamie. > He sent an email with the corrected dates. Debian release occurs every 2 years. The last release one was last year. The next one will be next year. -- Cheers, Leandro Cunha Software Engineer and Debian Contributor
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
On Mon, Mar 14 2022, Paul Gevers wrote: > We are currently considering the following dates as our freeze > dates. If you are aware of major clashes of these dates with anything > we depend on please let us know. We also like to stress again that we > really would like to have a short Hard and Full Freeze (counting in > weeks, rather than months), so please plan accordingly. If serious > delays turn up during any of the Freeze steps, we rather (partially or > completely) thaw bookworm again than staying frozen for a long time. > > 2022-01-12 - Milestone 1 - Transition and toolchain freeze > 2022-02-12 - Milestone 2 - Soft Freeze > 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and > packages without autopkgtests > To be announced - Milestone 4 - Full Freeze Have not all of these dates already past? Or are these milestones over three consecutive days in December of this year? jamie.
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
Hi Paul, These dates are in the past, was it intended for the dates to be in Janruay, February, and March of 2023 instead of 2022? Jesse On 2022-03-14 5:36 p.m., Paul Gevers wrote: > Dear all, > > We are currently considering the following dates as our freeze > dates. If you are aware of major clashes of these dates with anything > we depend on please let us know. We also like to stress again that we > really would like to have a short Hard and Full Freeze (counting in > weeks, rather than months), so please plan accordingly. If serious > delays turn up during any of the Freeze steps, we rather (partially or > completely) thaw bookworm again than staying frozen for a long time. > > 2022-01-12 - Milestone 1 - Transition and toolchain freeze > 2022-02-12 - Milestone 2 - Soft Freeze > 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and > packages without autopkgtests > To be announced - Milestone 4 - Full Freeze > > On behalf of the Release Team, > Paul > > >
Re: Bits from the Release Team: bookworm freeze dates (preliminary)
On Mon, Mar 14, 2022 at 9:36 PM Paul Gevers wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Dear all, > > We are currently considering the following dates as our freeze > dates. If you are aware of major clashes of these dates with anything > we depend on please let us know. We also like to stress again that we > really would like to have a short Hard and Full Freeze (counting in > weeks, rather than months), so please plan accordingly. If serious > delays turn up during any of the Freeze steps, we rather (partially or > completely) thaw bookworm again than staying frozen for a long time. > > 2022-01-12 - Milestone 1 - Transition and toolchain freeze > 2022-02-12 - Milestone 2 - Soft Freeze > 2022-03-12 - Milestone 3 - Hard Freeze - for key packages and > packages without autopkgtests > To be announced - Milestone 4 - Full Freeze > > On behalf of the Release Team, > Paul > Is it possible to adopt ISO8601 dates like -MM-DD please (to avoid heart attacks) ? Jérémy
Bits from the Release Team: bookworm freeze dates (preliminary)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [Message resent because the year was wrong] Dear all, We are currently considering the following dates as our freeze dates. If you are aware of major clashes of these dates with anything we depend on please let us know. We also like to stress again that we really would like to have a short Hard and Full Freeze (counting in weeks, rather than months), so please plan accordingly. If serious delays turn up during any of the Freeze steps, we rather (partially or completely) thaw bookworm again than staying frozen for a long time. 2023-01-12 - Milestone 1 - Transition and toolchain freeze 2023-02-12 - Milestone 2 - Soft Freeze 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and packages without autopkgtests To be announced - Milestone 4 - Full Freeze On behalf of the Release Team, Paul -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmIvqMAACgkQnFyZ6wW9 dQopRgf/dkqYGQlfN8vARfT3xWYzeGG76kRzIw/DeUFrW1QAm7Im47SMmvJjwfEy 8L7Q2F7DSZfn/1Njg3DnNHvIGHAXm43Kx8EkfEk3ek5IsroVKIwuxk5CmjS/4D/S 8E8zdNQll0BzjDb6oT58ySNRB1+W2TM9GvDQ2ozZJ0JAlOHg5GMtd0veUXDyJ1Gt Vs0iHZrXgBQ4GTXI4Ig9npeYCrTAJMO0Pbm0JkyutaHECJ+ES1hRDG/tkiVoqPbZ JwKtZFJH5RwkSe8iBVwPJl0pEvZpQG/4ODTWGJsoGURPlauVEgCE40Z+24aWzkQA /OlzV92SVvXakwlpnz2Xx/FpAJbPQQ== =gUm+ -END PGP SIGNATURE- OpenPGP_signature Description: OpenPGP digital signature
