Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #94580 > unrolled thread
| Started by | Jonathan Wiltshire <jmw@debian.org> |
|---|---|
| First post | 2026-10-22 21:30 +0200 |
| Last post | 2026-10-30 16:00 +0100 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Planning point release dates for 2026 Q4, 2027 H1 Jonathan Wiltshire <jmw@debian.org> - 2026-10-22 21:30 +0200
Re: Planning point release dates for 2026 Q4, 2027 H1 Jonathan Wiltshire <jmw@debian.org> - 2026-10-30 16:00 +0100
| From | Jonathan Wiltshire <jmw@debian.org> |
|---|---|
| Date | 2026-10-22 21:30 +0200 |
| Subject | Re: Planning point release dates for 2026 Q4, 2027 H1 |
| Message-ID | <NR6E9-7f8A-1@gated-at.bofh.it> |
On Sat, Sep 12, 2026 at 06:34:33PM +0100, Steve McIntyre wrote: > Crap, just discussing future releases with the images team and I > realise I never responded to this... > > On Mon, Apr 06, 2026 at 09:49:58PM +0100, Jonathan Wiltshire wrote: > >Hi, > > > >I am proposing the following dates for trixie point releases for the end of > >2026 and first half 2027: > > > >13.8 14 November 2026 > > That's the weekend after the miniconf in Cambridge, which makes things > awkward. Pushing back a week later would be appreciated by people, I think. Yes - 21st Nov 2026? > >13.9 9 January 2027 > > That close to New Year (for prep) also sounds worrying - a week later > again please? Yes - 16th Jan 2027? > >13.10 13 March 2027 > >13.11 8 May 2027 > > > >If any of these cause your teams problems please let me know by the end of > >April, when I will freeze and publish these. > > And we've also spotted that your mail only went to d-release, so > several other members of the images team never saw it to comment. Was > that deliberate? Pants, no. The magic BCC alias should have taken care of that, although I'm not actually sure what it expands to. Does this mail reach the right places? -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
[toc] | [next] | [standalone]
| From | Jonathan Wiltshire <jmw@debian.org> |
|---|---|
| Date | 2026-10-30 16:00 +0100 |
| Message-ID | <NTWff-8Pux-3@gated-at.bofh.it> |
| In reply to | #94580 |
On Fri, Oct 23, 2026 at 12:48:16AM +0100, Steve McIntyre wrote: > On Thu, Oct 22, 2026 at 11:57:10PM +0200, Cyril Brulebois wrote: > >Hi, > > > >Jonathan Wiltshire <jmw@debian.org> (2026-10-22): > >> Yes - 21st Nov 2026? > >[…] > >> Yes - 16th Jan 2027? > > > >Still virtually fine with anything you can come up with. > > > >> Pants, no. The magic BCC alias should have taken care of that, > >> although I'm not actually sure what it expands to. Does this mail > >> reach the right places? > > > >Even if your mail reaches the right places, reply-all only goes to > >debian-release@ and yourself (which I'm only realizing now is what > >happened with my first reply), so that's not terribly useful for > >cross-team communication. > > ACK, good point. It is. Mega-CC for now then until I work out something better. So let's say 21st Nov and 16th Jan for the next two, and the rest as scheduled but there is time to adjust them yet. The schedule as originally planned is https://release.debian.org Please alert me to any problems. -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web