After some discusion we'll leave 11.8 until its proper cadence in September
and combine it with 12.2.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC
On 6/26/23 12:26, Adam D. Barratt wrote:
Hi Donald,
On Wed, 2023-06-21 at 06:33 -0400, Donald Norwood wrote:
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
Hi Donald,
On Wed, 2023-06-21 at 06:33 -0400, Donald Norwood wrote:
> 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
Can help the 1th or 8th July the 15th i am having vacation
2023-06-19 23:02 GMT+02:00, Jonathan Wiltshire :
> 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
On Sat, Jun 24, 2023 at 03:17:22PM +0100, Jonathan Wiltshire wrote:
>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
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
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
On Mon, 2023-06-19 at 22:02 +0100, Jonathan Wiltshire wrote:
> 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
On Mon, Jun 19, 2023 at 10:02:27PM +0100, Jonathan Wiltshire wrote:
>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
On Mon, 19, Jun, 2023 at 10:02:27PM +0100, Jonathan Wiltshire spoke thus..
> 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.
>
>
Hi,
On 6/19/23 17:02, Jonathan Wiltshire wrote:
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
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
Hi,
Jonathan Wiltshire (2023-06-19):
> 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
13 matches
Mail list logo
