Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On 8/2/22 01:01, Otavio Salvador wrote: Em seg., 1 de ago. de 2022 às 19:41, Richard Purdie > escreveu: I do feel that whilst well intentioned, there are too many ways it can go wrong in ways that will cause bad feelings towards the

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

Hi, On Tue, Aug 02, 2022 at 08:18:46AM +0200, Philip Balister wrote: > We are trying to use technology to solve a social problem. No amount of > tweaking the code will stop people from making poor choices. > > How can we do a better job of communicating bad practices to the user baser? > Do we

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On 8/2/22 10:13, Michael Opdenacker via lists.openembedded.org wrote: Greetings, Exactly. I filed a bug about this last year but I don't know how to fix it. In a few words, I'd like to add "Supported until MM/" to the description of each supported release. This could help people to make

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

Greetings, On 8/2/22 09:33, Mikko Rapeli wrote: Hi, On Tue, Aug 02, 2022 at 08:18:46AM +0200, Philip Balister wrote: We are trying to use technology to solve a social problem. No amount of tweaking the code will stop people from making poor choices. How can we do a better job of

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On Tue, 2022-08-02 at 10:08 +0200, Alexander Kanavin wrote: > I tend to agree that warnings popping out of nowhere when the stable > branch is close to (or beyond) EOL is 'too late' - if you got yourself > into that situation, you're likely to have a broader maintainability > problem. > >

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On Tue, Aug 2, 2022 at 1:08 AM Alexander Kanavin wrote: > > On Tue, 2 Aug 2022 at 09:58, Andre McCurdy wrote: > > Who is the user base you're referring to? The end customer? They don't > > see build logs or EOL warnings. The OEM creating releases to add new > > features to the boxes in the

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On Tue, 2 Aug 2022 at 09:58, Andre McCurdy wrote: > Who is the user base you're referring to? The end customer? They don't > see build logs or EOL warnings. The OEM creating releases to add new > features to the boxes in the field? They would see the EOL warnings, > but don't have skills or

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On Mon, Aug 1, 2022 at 11:18 PM Philip Balister wrote: > > On 8/2/22 01:01, Otavio Salvador wrote: > > > > Em seg., 1 de ago. de 2022 às 19:41, Richard Purdie > > > > escreveu: > > > > I do feel that whilst well intentioned, there are too many ways

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On Tue, 2 Aug 2022 at 10:28, Andre McCurdy wrote: > If your goal is to educate users who might now be aware of the OE > release cycles then just put a banner such as "This is OE 3.1, > expected to be supported until at least xxx" as the start of every > build. No need to wait until EOL, just

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

On Tue, Aug 02, 2022 at 10:13:11AM +0200, Michael Opdenacker via lists.openembedded.org wrote: > Greetings, > > On 8/2/22 09:33, Mikko Rapeli wrote: > >Hi, > > > >On Tue, Aug 02, 2022 at 08:18:46AM +0200, Philip Balister wrote: > >>We are trying to use technology to solve a social problem. No