Re: [yocto-status] Yocto Project release dates for May 2026 to April 2027

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

Hi Paul,
This is great.  Having 12 months of clarity greatly helps in planning the
AGL schedule since we usually put our schedules together 12 months in
advance. I have traditionally used guessed dates in planning and kept track
of which are guesses and which are provided by the project.

I think a quarterly review might be beneficial so you can adjust any dates
accordingly if things have slipped.  Having the complete picture of  the
upcoming year by early November would be a big help in my planning.

Regards,
Walt



Walt Miner
AGL Community Manager
The Linux Foundation

Visit us at:
www.automotivegradelinux.org
lists.automotivelinux.org
www.linuxfoundation.org




On Wed, Apr 1, 2026 at 10:24=E2=80=AFAM Paul Barker via lists.yoctoproject.=
org
<[email protected]> wrote:

> Hi all,
>
> I'm happy to propose the following Yocto Project release dates, covering
> the period of May 2026 to April 2027.
>
> In order to make planning easier for downstream users, we're setting
> these dates for a full year instead of just 6 months. The increased
> horizon, and the focus on getting ready to build 6.0 M3 does mean that
> there's been a little delay getting the dates out, but this should
> hopefully put people in a good place to plan now.
>
> We will review these again in 6 months time to see if any adjustments
> are needed to the 2027 dates. I'd also like to get dates in the calendar
> up to Nov 2027 some time in October this year.
>
>
> Notes
> =3D=3D=3D=3D=3D
>
> - All dates are **week commencing**, the exact day the release is
>   published depends on TSC availability to approve releases and time
>   taken to upload release artifacts.
>
> - Releases will be built 10-14 days before the target release date to
>   give time for QA and review.
>
> - We aim for 6-7 weeks between releases in each series, occasionally
>   there will be an 8 week gap due to things like Christmas/New Year
>   vacations.
>
> - We aim for 4 weeks between .0 and .1 releases to allow us to get any
>   necessary fixes out for the new series.
>
>
> Feedback
> =3D=3D=3D=3D=3D=3D=3D=3D
>
> Please review these and let me know if you have any feedback before the
> next weekly tech call on Tues 7th April.
>
> I'd especially like to know:
>   **Is 12 months of dates beneficial to you, vs just having 6 months?**
>
> It does take more coordination to plan with a longer horizon.
>
>
> 5.0 "scarthgap" series
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> 5.0.18  : w/c 2026-05-25
> 5.0.19  : w/c 2026-07-13
> 5.0.20  : w/c 2026-08-31
> 5.0.21  : w/c 2026-10-19
> 5.0.22  : w/c 2026-12-14
> 5.0.23  : w/c 2027-01-25
> 5.0.24  : w/c 2027-03-08
> 5.0.25  : w/c 2027-04-19
>
>
> 6.0 "wrynose" series
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> 6.0.0   : w/c 2026-05-04
> 6.0.1   : w/c 2026-06-01
> 6.0.2   : w/c 2026-07-06
> 6.0.3   : w/c 2026-08-24
> 6.0.4   : w/c 2026-10-12
> 6.0.5   : w/c 2026-12-07
> 6.0.6   : w/c 2027-01-18
> 6.0.7   : w/c 2027-03-01
> 6.0.8   : w/c 2027-04-12
>
>
> 6.1 series
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> 6.1 M1  : w/c 2026-06-22
> 6.1 M2  : w/c 2026-08-03
> 6.1 M3  : w/c 2026-09-14
> 6.1.0   : w/c 2026-11-02
> 6.1.1   : w/c 2026-11-30
> 6.1.2   : w/c 2027-01-04
> 6.1.3   : w/c 2027-02-22
> 6.1.4   : w/c 2027-04-05
>
>
> 6.2 series
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> 6.2 M1  : w/c 2026-12-21
> 6.2 M2  : w/c 2027-02-01
> 6.2 M3  : w/c 2027-03-15
> 6.2.0   : w/c 2027-05-03
>
>
> Best regards,
>
> --
> Paul Barker
>
>
>
>=20
>
>
>

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

<div dir=3D"ltr"><div>Hi Paul,=C2=A0</div><div>This is great.=C2=A0 Having =
12 months of clarity greatly helps in planning the AGL schedule since we us=
ually put our schedules together 12 months in advance. I have traditionally=
 used guessed dates in planning and kept track of which are guesses and whi=
ch are provided by the project. =C2=A0</div><div><br></div><div>I think a q=
uarterly=C2=A0review might be beneficial so you can adjust any dates accord=
ingly if things have slipped.=C2=A0 Having the complete picture of =C2=A0th=
e upcoming year by early November would be a big help in my planning.</div>=
<div><br></div><div>Regards,</div><div>Walt</div><div><br></div><div><br></=
div><div><br></div><div><div dir=3D"ltr" class=3D"gmail_signature" data-sma=
rtmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr"><span style=3D"color:rgb(136,136,136)">=
Walt Miner</span></div><div dir=3D"ltr"><div style=3D"color:rgb(136,136,136=
)">AGL Community Manager</div><div style=3D"color:rgb(136,136,136)">The Lin=
ux Foundation<br></div><div style=3D"color:rgb(136,136,136)"><br></div><div=
 style=3D"color:rgb(136,136,136)">Visit us at:</div><div style=3D"color:rgb=
(136,136,136)"><a href=3D"http://www.automotivegradelinux.org" target=3D"_b=
lank">www.automotivegradelinux.org</a></div><div style=3D"color:rgb(136,136=
,136)"><a href=3D"http://lists.automotivelinux.org" target=3D"_blank">lists=
.automotivelinux.org</a></div><div style=3D"color:rgb(136,136,136)"><a href=
=3D"http://www.linuxfoundation.org" target=3D"_blank">www.linuxfoundation.o=
rg</a></div><div style=3D"color:rgb(136,136,136)"><br></div><div style=3D"c=
olor:rgb(136,136,136)"><br></div></div></div></div></div></div></div></div>=
</div></div></div></div></div><br></div><br><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr 1, 2026=
 at 10:24=E2=80=AFAM Paul Barker via <a href=3D"http://lists.yoctoproject.o=
rg">lists.yoctoproject.org</a> &lt;paul=3D<a href=3D"mailto:pbarker.dev@lis=
ts.yoctoproject.org">[email protected]</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,2=
04);padding-left:1ex">Hi all,<br>
<br>
I&#39;m happy to propose the following Yocto Project release dates, coverin=
g<br>
the period of May 2026 to April 2027.<br>
<br>
In order to make planning easier for downstream users, we&#39;re setting<br=
>
these dates for a full year instead of just 6 months. The increased<br>
horizon, and the focus on getting ready to build 6.0 M3 does mean that<br>
there&#39;s been a little delay getting the dates out, but this should<br>
hopefully put people in a good place to plan now.<br>
<br>
We will review these again in 6 months time to see if any adjustments<br>
are needed to the 2027 dates. I&#39;d also like to get dates in the calenda=
r<br>
up to Nov 2027 some time in October this year.<br>
<br>
<br>
Notes<br>
=3D=3D=3D=3D=3D<br>
<br>
- All dates are **week commencing**, the exact day the release is<br>
=C2=A0 published depends on TSC availability to approve releases and time<b=
r>
=C2=A0 taken to upload release artifacts.<br>
<br>
- Releases will be built 10-14 days before the target release date to<br>
=C2=A0 give time for QA and review.<br>
<br>
- We aim for 6-7 weeks between releases in each series, occasionally<br>
=C2=A0 there will be an 8 week gap due to things like Christmas/New Year<br=
>
=C2=A0 vacations.<br>
<br>
- We aim for 4 weeks between .0 and .1 releases to allow us to get any<br>
=C2=A0 necessary fixes out for the new series.<br>
<br>
<br>
Feedback<br>
=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
Please review these and let me know if you have any feedback before the<br>
next weekly tech call on Tues 7th April.<br>
<br>
I&#39;d especially like to know:<br>
=C2=A0 **Is 12 months of dates beneficial to you, vs just having 6 months?*=
*<br>
<br>
It does take more coordination to plan with a longer horizon.<br>
<br>
<br>
5.0 &quot;scarthgap&quot; series<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
5.0.18=C2=A0 : w/c 2026-05-25<br>
5.0.19=C2=A0 : w/c 2026-07-13<br>
5.0.20=C2=A0 : w/c 2026-08-31<br>
5.0.21=C2=A0 : w/c 2026-10-19<br>
5.0.22=C2=A0 : w/c 2026-12-14<br>
5.0.23=C2=A0 : w/c 2027-01-25<br>
5.0.24=C2=A0 : w/c 2027-03-08<br>
5.0.25=C2=A0 : w/c 2027-04-19<br>
<br>
<br>
6.0 &quot;wrynose&quot; series<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
6.0.0=C2=A0 =C2=A0: w/c 2026-05-04<br>
6.0.1=C2=A0 =C2=A0: w/c 2026-06-01<br>
6.0.2=C2=A0 =C2=A0: w/c 2026-07-06<br>
6.0.3=C2=A0 =C2=A0: w/c 2026-08-24<br>
6.0.4=C2=A0 =C2=A0: w/c 2026-10-12<br>
6.0.5=C2=A0 =C2=A0: w/c 2026-12-07<br>
6.0.6=C2=A0 =C2=A0: w/c 2027-01-18<br>
6.0.7=C2=A0 =C2=A0: w/c 2027-03-01<br>
6.0.8=C2=A0 =C2=A0: w/c 2027-04-12<br>
<br>
<br>
6.1 series<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
6.1 M1=C2=A0 : w/c 2026-06-22<br>
6.1 M2=C2=A0 : w/c 2026-08-03<br>
6.1 M3=C2=A0 : w/c 2026-09-14<br>
6.1.0=C2=A0 =C2=A0: w/c 2026-11-02<br>
6.1.1=C2=A0 =C2=A0: w/c 2026-11-30<br>
6.1.2=C2=A0 =C2=A0: w/c 2027-01-04<br>
6.1.3=C2=A0 =C2=A0: w/c 2027-02-22<br>
6.1.4=C2=A0 =C2=A0: w/c 2027-04-05<br>
<br>
<br>
6.2 series<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
6.2 M1=C2=A0 : w/c 2026-12-21<br>
6.2 M2=C2=A0 : w/c 2027-02-01<br>
6.2 M3=C2=A0 : w/c 2027-03-15<br>
6.2.0=C2=A0 =C2=A0: w/c 2027-05-03<br>
<br>
<br>
Best regards,<br>
<br>
-- <br>
Paul Barker<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div>

--000000000000bb2769064e677927--