[OE-core] [RFC] [PATCH] Provide users with project support status

[Adrian Bunk]

On Sat, Nov 02, 2019 at 12:01:38PM +0100, Alexander Kanavin wrote:
> I too think that the information may never reach the target audience, as
> they could never update their builds to the point where it would start
> printing 'end of life'.
> 
> What could work instead is printing a link to the wiki during
> 'oe-init-build-env'.

What should the user do based on this link?

Currently the wiki does not even state EOL dates for supported releases,
and it is not made clear that "Community" is just an euphemism for EOL.

Many products are just using the example BSP provided with the reference 
hardware.

With Ubuntu most 3rd party development happens to their LTS releases,
and when the example BSP for the reference hardware is based on Ubuntu
it is usually based on an LTS release.

Many Yocto questions are coming from people who seem to be just starting
a new project based on an already no longer upstream supported Yocto
release.

The easiest way to get long-term security support in such a situation
is often to take the required parts from the BSP layer, and use them
to build the product on top of Ubuntu LTS (or Debian).

The core question should really be how to increase the time of upstream 
support that is usually left when a Yocto-based distibution reaches the 
user, not just how to tell users that they are screwed.

> Alex

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