On Thu, Oct 22, 2026 at 08:24:26PM +0100, Jonathan Wiltshire wrote: >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?
Is clear for me. Penciled in. >> >13.9 9 January 2027 >> >> That close to New Year (for prep) also sounds worrying - a week later >> again please? > >Yes - 16th Jan 2027? Is no longer clear for me, I'm afraid. 23rd looks better. >> >13.10 13 March 2027 >> >13.11 8 May 2027 These are clear for me so far. >> >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? I got this mail direct, and checking logs here I also saw it come in to: * debian-boot@ * debian-cd@ * debian-kernel@ * debian-live@ * debian-project@ * debian-release@ * debian-security@ * debian-www@ -- Steve McIntyre, Cambridge, UK. [email protected] "C++ ate my sanity" -- Jon Rabone
