From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Gatesgarth Maintainer
Date: Sun, 01 Nov 2020 13:39:56 +0000 [thread overview]
Message-ID: <f9234c1de8b2c54dae4cf406d39435858c4364e5.camel@linuxfoundation.org> (raw)
Hi,
With the gatesgarth release imminent, we need to think about how we
plan to maintain it. Its scheduled to run for around 7-8 months until
the next release comes out.
I did talk with Steve and we concluded he doesn't have the bandwidth to
handle gatesgarth as well as dunfell. I personally know how hard it is
for one maintainer to try and track patch status in multiple branches
for something with as many moving pieces are core.
Do we have anyone interested in helping with Gatesgarth stable branch
maintenance?
Cheers,
Richard
next reply other threads:[~2020-11-01 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 13:39 Richard Purdie [this message]
2020-11-01 23:53 ` [OE-core] Gatesgarth Maintainer Anuj Mittal
2020-11-05 23:22 ` Richard Purdie
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=f9234c1de8b2c54dae4cf406d39435858c4364e5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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