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

Hi, On August 2, 2022 8:58:47 PM GMT+02:00, Denys Dmytriyenko wrote: >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

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

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 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, 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 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, 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?

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 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?

Em seg., 1 de ago. de 2022 às 19:41, Richard Purdie < richard.pur...@linuxfoundation.org> 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 project. > What about security flaws that aren't fixed and

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

On Mon, 2022-08-01 at 19:30 +0200, Alexander Kanavin wrote: > On Mon, 1 Aug 2022 at 13:22, Ross Burton wrote: > > Would this be something done in oe-core, or something that distros > > (such as Poky) can opt in to? We don’t want to start warning when > > oe-core is EOL if the user is using a

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

Em seg., 1 de ago. de 2022 às 14:30, Alexander Kanavin < alex.kana...@gmail.com> escreveu: > On Mon, 1 Aug 2022 at 13:22, Ross Burton wrote: > > Would this be something done in oe-core, or something that distros (such > as Poky) can opt in to? We don’t want to start warning when oe-core is EOL

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

On Mon, 1 Aug 2022 at 13:22, Ross Burton wrote: > Would this be something done in oe-core, or something that distros (such as > Poky) can opt in to? We don’t want to start warning when oe-core is EOL if > the user is using a commercial Yocto release which still has support for many > years. >

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

Hi Alex, On 25 Jul 2022, at 19:13, Alexander Kanavin via lists.openembedded.org wrote: > an idea just popped into my head that I don't remember having been discussed: > > Should stable-branch oe-core issue a warning via bitbake when it is > close to EOL and perhaps a stronger warning when it

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

action plan Thanks, Ruslan From: openembedded-architecture@lists.openembedded.org on behalf of Alexander Kanavin Sent: Monday, July 25, 2022 9:13 PM To: openembedded-architecture Subject: [Openembedded-architecture] should oe-core issue a warning when it reaches

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

I don't like the idea at all, just because I feel that it will be based on a datetime (or some other criteria) to issue this warning, which will prevent use cases where ppl do a fork and maintain them on their own. In my opinion everyone should be aware of the lifecycle of the releases

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

Em seg., 25 de jul. de 2022 às 15:13, Alexander Kanavin < alex.kana...@gmail.com> escreveu: > an idea just popped into my head that I don't remember having been > discussed: > > Should stable-branch oe-core issue a warning via bitbake when it is > close to EOL and perhaps a stronger warning when

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

Hello, an idea just popped into my head that I don't remember having been discussed: Should stable-branch oe-core issue a warning via bitbake when it is close to EOL and perhaps a stronger warning when it has crossed it? I feel that this page: https://wiki.yoctoproject.org/wiki/Releases is not