From: Steve Sakoman <steve@sakoman.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
",openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Final nanbield release build on March 25, 2024
Date: Sun, 10 Mar 2024 07:19:22 -1000 [thread overview]
Message-ID: <CAOSpxdbz+nwUUWzLqt8oYfmU_2oP=9rFSWa33eyjBfi=MZv_2A@mail.gmail.com> (raw)
In-Reply-To: <CA+chaQdtaqzvpKqT3JHxBn7bSb8pfPAro4e_uOSjDMypqYcVqQ@mail.gmail.com>
On Sun, Mar 10, 2024 at 6:54 AM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> Hi Steve,
>
> I'm not using nanbield, but does
> https://wiki.yoctoproject.org/wiki/Releases need to be updated? It
> says "Support for 7 months (until May 2024)" so I was expecting final
> call for dunfell (which says "Long Term Support (until Apr. 2024¹))
> before nanbield.
I work to the release schedule that Stephen sends out each week, the
most recent being:
Upcoming dot releases:
YP 4.3.3 was released.
YP 3.1.32 is in QA.
YP 3.1.32 Release date 2024/03/15
YP 4.0.17 build date 2024/03/11
YP 4.0.17 Release date 2024/03/22
YP 4.3.4 build date 2024/03/25
YP 4.3.4 Release date 2024/04/05
YP 3.1.33 build date 2024/04/15
YP 3.1.33 Release date 2024/04/26
YP 4.0.18 build date 2024/04/22
YP 4.0.18 Release date 2024/05/03
YP 4.0.19 build date 2024/06/03
YP 4.0.19 Release date 2024/06/14
So the final nanbield release comes before the final dunfell release.
I will send out a similar final call for dunfell patches.
Steve
> On Sun, Mar 10, 2024 at 5:11 PM Steve Sakoman <steve@sakoman.com> wrote:
> >
> > If you have any patches you would like to submit for nanbield before
> > it goes EOL, please do so now!
> >
> > I'll be taking patches until around March 18 in preparation for a
> > March 25 build.
> >
> > Steve
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#196900): https://lists.openembedded.org/g/openembedded-core/message/196900
> > Mute This Topic: https://lists.openembedded.org/mt/104846319/3617156
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [martin.jansa@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
prev parent reply other threads:[~2024-03-10 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 16:11 Final nanbield release build on March 25, 2024 Steve Sakoman
2024-03-10 16:54 ` [OE-core] " Martin Jansa
2024-03-10 17:19 ` Steve Sakoman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOSpxdbz+nwUUWzLqt8oYfmU_2oP=9rFSWa33eyjBfi=MZv_2A@mail.gmail.com' \
--to=steve@sakoman.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).