All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "raj.khem@gmail.com" <raj.khem@gmail.com>,
	"Openembedded-devel@lists.openembedded.org"
	<Openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] Stable branch maintainership
Date: Tue, 9 Sep 2025 02:55:51 +0000	[thread overview]
Message-ID: <b83737ff4babe05615dc2dc7a63321328add6fc4.camel@intel.com> (raw)
In-Reply-To: <CAMKF1sqhzO979KgHE9BEfbw5xe7NH0GKZji9VHOAy6pn+E9NDQ@mail.gmail.com>

On Mon, 2025-09-08 at 14:47 -0700, Khem Raj via lists.openembedded.org
wrote:
> Dear Community members,
> 
> Armin has been doing awesome work in maintaining stable release for
> meta-openembedded layers for many releases, however his situation has
> changed such that he is not able to continue the meta-oe stable
> maintenance.
> 
> We have three branches in maintenance, kirstone, scarthgap and
> walnascar at the moment and
> a backlog has been piling up. Several members have raised concerns on
> mailing lists on pending
> updates for the stable branches
> 
> I would love to have someone step up to help with the stable
> maintainers role. Which would
> be looking for stable branch patches on mailing lists and reviewing
> them and creating a staging
> branch ( like contrib/stable/kirkstone-nut etc ), testing and
> preparing final pull.

I would be happy to take on this work.

Thanks,

Anuj

  reply	other threads:[~2025-09-09  2:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 21:47 Stable branch maintainership Khem Raj
2025-09-09  2:55 ` Mittal, Anuj [this message]
2025-09-09 15:34 ` [oe] " Gyorgy Sarvari
2025-09-11 18:54 ` Khem Raj
2025-09-18  2:49   ` Khem Raj
2025-09-18  6:30     ` [oe] " Marko, Peter
2025-09-18  7:14     ` Ashish Mishra
2025-09-18  7:24       ` [oe] " Gyorgy Sarvari

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=b83737ff4babe05615dc2dc7a63321328add6fc4.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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.