public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "akuster" <akuster808@gmail.com>
To: Martin Jansa <Martin.Jansa@gmail.com>, akuster <akuster808@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"poky@yoctoproject.org" <poky@yoctoproject.org>,
	"bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>,
	poky@lists.yoctoproject.org
Subject: Re: [bitbake-devel] [poky] Thud community support
Date: Wed, 29 Apr 2020 07:53:21 -0700	[thread overview]
Message-ID: <dc37c701-80de-6719-8d8b-6d8dcd1771f4@gmail.com> (raw)
In-Reply-To: <CA+chaQc8q4Nb4p76WPr=R7ocpDJ8CY3VnJ-k9W8bWW8nwMtYTw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]



On 4/28/20 11:10 AM, Martin Jansa wrote:
> Is Thud EOL now?
Go question.

>
> Or did someone volunteer off-list and now it waits for Maintainer
> selection process to be defined?
I received two inquires privately and forwarded them to Richard. I have
not had time to document the community maintainer selection process. The
ultimate decision will always be on the Repo maintainer which in this
case is Richard.

- armin

> https://wiki.yoctoproject.org/wiki/Releases still says Community support.
>
> Thanks
>
> On Tue, Mar 17, 2020 at 10:13 PM akuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
>
>
>     On 3/13/20 11:03 AM, akuster via Lists.Yoctoproject.Org
>     <http://Lists.Yoctoproject.Org> wrote:
>>     The Poky thud branch is now under 'Community support' and is seeking a
>>     maintainer to continue supporting the following repos for the thud release:
>>
>>     bitbake, core, meta-yocto and yocto-docs.
>>
>>
>>     There will be no more point releases.
>>
>>     see
>>     https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Maintainer_Procedures 
>>     to get an idea on what is expected.
>>
>>     The one thing we (YP) don't know is if there will be AutoBuilder
>>     resources available.  Please contact me or Richard regarding that statement.
>>
>>     If no one steps up by April 24th (six weeks -ish from now), Thud will be
>>     moved to EOL status.
>
>     It was pointed out to me that there is no Maintainer selection
>     process or criteria defined.  This  will have to be sorted out
>     before we move forward on this transition.
>
>
>     - armin
>
>>     - Armin
>>
>>
>>
>>
>
>
>
> 


[-- Attachment #2: Type: text/html, Size: 3801 bytes --]

  reply	other threads:[~2020-04-29 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15FBEF1FC40D189D.8114@lists.yoctoproject.org>
2020-03-17 21:12 ` [poky] Thud community support akuster808
2020-04-28 18:10   ` Martin Jansa
2020-04-29 14:53     ` akuster [this message]
2020-05-04  7:41       ` [bitbake-devel] " Daniels Umanovskis

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=dc37c701-80de-6719-8d8b-6d8dcd1771f4@gmail.com \
    --to=akuster808@gmail.com \
    --cc=Martin.Jansa@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@lists.yoctoproject.org \
    --cc=poky@yoctoproject.org \
    --cc=yocto@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