From: Adrian Bunk <bunk@stusta.de>
To: Ruslan Bilovol <ruslan.bilovol@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] [PATCH] Provide users with project support status
Date: Fri, 1 Nov 2019 22:12:25 +0200 [thread overview]
Message-ID: <20191101201225.GA1826@localhost> (raw)
In-Reply-To: <20191101184638.31898-1-ruslan.bilovol@gmail.com>
On Fri, Nov 01, 2019 at 07:46:38PM +0100, Ruslan Bilovol wrote:
> When OE/Yocto project goes through its lifecycle, there
> is no any way to identify where it is other than go
> to a Yocto wiki and look at current status.
The status in the wiki can be updated.
> Moreover, change from maintained to community maintained
> end EOLing happens silently so users not always know
> about that.
>
> This patch aims to remove this gap. The status should
> be changed so users can clearly identify at which point
> it is now:
> Development -> Stable -> Community supported -> End Of Life
>
> It is now printed during the build.
>...
What is printed is the status at the point in the
(sometime distant) past when a release was made.
It is not uncommon for hardware to come with an example BSP based
on an older release like for example Yocto 2.0.3 (sic) today.
The Yocto 2.0.3 release shipped as part of this distribution would
never print "End Of Life".
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-11-01 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 18:46 [RFC] [PATCH] Provide users with project support status Ruslan Bilovol
2019-11-01 19:02 ` ✗ patchtest: failure for " Patchwork
2019-11-01 20:12 ` Adrian Bunk [this message]
2019-11-02 11:01 ` [RFC] [PATCH] " Alexander Kanavin
2019-11-02 13:19 ` Andrey Zhizhikin
2019-11-02 15:30 ` Adrian Bunk
2019-11-02 15:54 ` Alexander Kanavin
2019-11-02 21:10 ` Adrian Bunk
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=20191101201225.GA1826@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ruslan.bilovol@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox