Re: Perl 5.45.x release schedule

--000000000000ced240065744c887
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 23, 2026 at 11:21=E2=80=AFAM Paul "LeoNerd" Evans <
[email protected]> wrote:

> Technically a decision for PSC but I'll collect ideas from here: I'm
> considering what the release schedule should look like for the 5.45.x
> releases going into 5.46.
>
> I think it's uncontentious to say that we slipped the timeline for 5.44
> due to a number of factors, and would like to get back to "target May
> 20th" time for the 5.46 release. With that in mind, I think we have a
> choice of two options to make:
>
>   Option 1) Perform the usual one-per-month bleadpoint releases, but do
>             one fewer of them this time to line up with that date
>
>   Option 2) Perform the same number of bleadpoint releases, but at a
>             slightly faster rate (at least, initially), so we can fit
>             them in shorter time
>
>             In particular for this, I think if we did the next four
>             releases at about 3-week intervals instead of our usual
>             monthly cycle, we'd get 5.45.6 back out on track thereafter.
>
> I have no firm opinion either way, so I'm happy to hear thoughts.


Effectively we slipped one, IMHO that's not so much that we need to change
our schedule. In 5.45.1 we already greatly reduced our backlog, I hope we
can eliminate it entirely in 5.45.2.

Leon

--000000000000ced240065744c887
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jul 23, 2026 at 11:21=E2=80=AFAM =
Paul &quot;LeoNerd&quot; Evans &lt;<a href=3D"mailto:[email protected]=
">[email protected]</a>&gt; wrote:</div><div class=3D"gmail_quote gmai=
l_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Techni=
cally a decision for PSC but I&#39;ll collect ideas from here: I&#39;m<br>
considering what the release schedule should look like for the 5.45.x<br>
releases going into 5.46.<br>
<br>
I think it&#39;s uncontentious to say that we slipped the timeline for 5.44=
<br>
due to a number of factors, and would like to get back to &quot;target May<=
br>
20th&quot; time for the 5.46 release. With that in mind, I think we have a<=
br>
choice of two options to make:<br>
<br>
=C2=A0 Option 1) Perform the usual one-per-month bleadpoint releases, but d=
o<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 one fewer of them this time to li=
ne up with that date<br>
<br>
=C2=A0 Option 2) Perform the same number of bleadpoint releases, but at a<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 slightly faster rate (at least, i=
nitially), so we can fit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 them in shorter time<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 In particular for this, I think i=
f we did the next four<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 releases at about 3-week interval=
s instead of our usual<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 monthly cycle, we&#39;d get 5.45.=
6 back out on track thereafter.<br>
<br>
I have no firm opinion either way, so I&#39;m happy to hear thoughts.</bloc=
kquote><div><br></div><div>Effectively we slipped one, IMHO that&#39;s not =
so much that we need to change our schedule. In 5.45.1 we already greatly r=
educed our backlog, I hope we can eliminate it entirely in 5.45.2.</div><di=
v><br></div><div>Leon</div></div></div>

--000000000000ced240065744c887--