From: Ryan Eatmon <reatmon@ti.com>
To: <mlynch@hi-techniques.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] Dunfell branch EOL ?
Date: Mon, 25 Mar 2024 09:43:43 -0500 [thread overview]
Message-ID: <683f783b-599d-4714-b1f6-def6659ce739@ti.com> (raw)
In-Reply-To: <O9SB.1711369070225727762.5uX5@lists.yoctoproject.org>
On 3/25/2024 7:17 AM, mlynch@hi-techniques.com wrote:
> There was an announcement in the #Yocto group about the Dunfell branch going to EOL. I was wondering, will TI still be pushing changes to that branch after it goes EOL or will changes only be pushed to different (newer) branch(s)? I'm asking because I've been using the Dunfell branch to build for the "beagle" platform(s) because I have not been successful at getting a build on any other branch (kirkstone or master) for that platform to boot.
We have not been pushing many things to dunfell since we switched to
kirkstone, and will likely not push that many changes to kirkstone once
scarthgap comes out. The majority of our efforts tend towards the
latest kernel/uboot versions and the latest LTS branch of yocto.
The EOL refers to pushing any new security patches/CVEs for many of the
packages out of oe-core. There will never be any plans to remove the
dunfell branch, so you are free to continue to use it if you cannot move
to any of the newer branches.
If you have any bugs to report against mater/kirkstone/scarthgap with
the beagle platform not booting properly, feel free to submit it.
There are currently 4 beagle boards supported in meta-ti-bsp, which one
are you specifically using?
--
Ryan Eatmon reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
prev parent reply other threads:[~2024-03-25 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:17 Dunfell branch EOL ? mlynch
2024-03-25 14:43 ` Ryan Eatmon [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=683f783b-599d-4714-b1f6-def6659ce739@ti.com \
--to=reatmon@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=mlynch@hi-techniques.com \
/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).