From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master][PATCH 0/3] Plan to better support non-LTS branches
Date: Wed, 17 Apr 2024 12:32:56 -0400 [thread overview]
Message-ID: <20240417163256.GN28791@denix.org> (raw)
In-Reply-To: <20240417161129.9697-1-reatmon@ti.com>
Thanks for doing this! This is pretty much exactly as we discussed yesterday,
so besides a minor comment/issue in patch #3, you have my Ack for the series.
On Wed, Apr 17, 2024 at 11:11:26AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> Since we do not directly support the non-LTS branches, customers are
> forced to rely on master for projects that make use of those branches.
> We are not going to start creating branches for all of the non-LTS
> releases, but we can do a better job of having master continue to
> support the branches that are still supported by the Yocto project [1].
>
> Recently we added and removed a patch to support the uboot mainline that
> required the python3-yamllint package. We were not thinking about
> customers trying to use the uboot mainline who might be currently locked
> into nanbield and not master.
>
> This series seeks to restore that reverted patch and create a system by
> which we can schedule the removal of these temporary patches.
> Additionaly it updates the compatible layer list to those with active
> support by the Yocto project [1].
>
> [1] https://wiki.yoctoproject.org/wiki/Releases
>
> Ryan Eatmon (3):
> python3-yamllint: Temporarily carry this new recipe
> TODO: Add TODO list
> conf/layer.conf: Update LAYERSERIES_COMPAT
>
> TODO | 9 +++++++++
> meta-ti-bsp/conf/layer.conf | 2 +-
> meta-ti-extras/conf/layer.conf | 2 +-
> .../python-yamllint/python3-yamllint_1.33.0.bb | 15 +++++++++++++++
> 4 files changed, 26 insertions(+), 2 deletions(-)
> create mode 100644 TODO
> create mode 100644 meta-ti-extras/recipes-devtools/python-yamllint/python3-yamllint_1.33.0.bb
>
> --
> 2.17.1
prev parent reply other threads:[~2024-04-17 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 16:11 [meta-ti][master][PATCH 0/3] Plan to better support non-LTS branches Ryan Eatmon
2024-04-17 16:11 ` [meta-ti][master][PATCH 1/3] python3-yamllint: Temporarily carry this new recipe Ryan Eatmon
2024-04-17 16:11 ` [meta-ti][master][PATCH 2/3] TODO: Add TODO list Ryan Eatmon
2024-04-17 16:11 ` [meta-ti][master][PATCH 3/3] conf/layer.conf: Update LAYERSERIES_COMPAT Ryan Eatmon
2024-04-17 16:30 ` Denys Dmytriyenko
2024-04-17 18:35 ` Ryan Eatmon
[not found] ` <17C7250D24373378.20815@lists.yoctoproject.org>
2024-04-17 18:36 ` Ryan Eatmon
2024-04-17 16:32 ` Denys Dmytriyenko [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=20240417163256.GN28791@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.