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 <[email protected]
> <mailto:[email protected]>> 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
>>
>>
>>
>>
>
>
>
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49274): https://lists.yoctoproject.org/g/yocto/message/49274
Mute This Topic: https://lists.yoctoproject.org/mt/73354124/21656
Group Owner: [email protected]
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/737036229/xyzzy  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to