I'm sending this separately to a similar mail for 12.1. That's because the timings are far enough out that they would make sense on separate weekends, but they could also be stretched[1] and combined.
Two months from 29th April is around the 1st July, so I propose:
1st July
8th July
15th July at a push
Hi,
I'm sending this separately to a similar mail for 12.1. That's because the >timings are far enough out that they would make sense on separate weekends, >but they could also be stretched[1] and combined.
Two months from 29th April is around the 1st July, so I propose:
1st July
8th July
15th July at a push
1: a shame that joke hasn't worked for some years now
Hi,
I'm sending this separately to a similar mail for 12.1. That's because the timings are far enough out that they would make sense on separate weekends, but they could also be stretched[1] and combined.
Two months from 29th April is around the 1st July, so I propose:
1st July
8th July
15th July at a push
I'm sending this separately to a similar mail for 12.1. That's
because the
timings are far enough out that they would make sense on separate
weekends,
but they could also be stretched[1] and combined.
Two months from 29th April is around the 1st July, so I propose:
1st July
8th July
15th July at a push
The traditional cadence for oldstable point releases is four months,
rather than two. That technically means that 11.8 would be due
somewhere in late August to mid-September. So we could either punt 11.8
so it aligns with 12.2 rather than 12.1, or do 11.8 together with 12.1
and then align 11.9 with 12.3.
I think I'd prefer the latter option, i.e. we do 11.8+12.1 in July,
12.2 probably September, then 11.9+12.3 Novemberish.
On Tue, Jun 20, 2023 at 06:15:30PM +0100, Adam D. Barratt wrote:
The traditional cadence for oldstable point releases is four months,
rather than two. That technically means that 11.8 would be due
somewhere in late August to mid-September. So we could either punt 11.8
so it aligns with 12.2 rather than 12.1, or do 11.8 together with 12.1
and then align 11.9 with 12.3.
I think I'd prefer the latter option, i.e. we do 11.8+12.1 in July,
12.2 probably September, then 11.9+12.3 Novemberish.
Yes, I had forgotten about the transition to oldstable candece. I was going >to suggest, though, that 11.8 gets pushed back to cadence with 12.2 and we >just do 12.1 on its own first. How does that sound?
Hi,
I'm sending this separately to a similar mail for 12.1. That's because the timings are far enough out that they would make sense on separate weekends, but they could also be stretched[1] and combined.
Two months from 29th April is around the 1st July, so I propose:
1st July
8th July
15th July at a push
1: a shame that joke hasn't worked for some years now
Thanks,
--
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
Hi,
On 6/20/23 13:15, Adam D. Barratt wrote:
The traditional cadence for oldstable point releases is four
months,
rather than two. That technically means that 11.8 would be due
somewhere in late August to mid-September. So we could either punt
11.8
so it aligns with 12.2 rather than 12.1, or do 11.8 together with
12.1
and then align 11.9 with 12.3.
...
The 1st would mean freezing this coming weekend, which is very
tight.
As per the 12.1 mail, either the 8th or 15th would work for me,
with a
preference for the latter. Given the explanation above though, I
think
the 22nd would be fine for 11.8 as well.
I think pushing everything forward at this time would be advisable
as several people have indicated that they need a breather. A slight
delay may be ideal.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 51:28:05 |
| Calls: | 6,712 |
| Calls today: | 5 |
| Files: | 12,243 |
| Messages: | 5,355,038 |
| Posted today: | 1 |