Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?
I remember that I proposed a similar idea on one of pre-covid OEDEM meetings during LTS discussions. We discussed at least two approaches: date-based (e.g. after some date bitbake will print the message) and last-commit based (e.g when maintainer EOLs the branch his last commit will patch OE so it will print the message) As far as I remember we also discussed disadvantages. For the date-based approach disadvantage was if someone forks the branch but in mainline maintainer decided to extend support, he will patch the EOL date in mainline, but forked branch won't have it and will post annoying message during the build. For the last-commit approach, if someone forks the branch he will never receive that last commit unless he merges it, and may think the branch is still maintained while it isn't. Another idea was to do bitbake online check if the release is still supported (e.g. bitbake reaches some OE/Yocto servers online) but that may not work for people who don't use Internet connection for the build (BB_NO_NETWORK option is enabled) There were also some other discussions of that, however I don't remember any details. As a bottom line, we discussed it, but didn't have any 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 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 enough to ensure the message (of not using EOL yocto) reaches the users, and we need something better and directly seen by anyone invoking bitbake. Is it a terrible idea? Awesome idea? Ok-ish idea? Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1598): https://lists.openembedded.org/g/openembedded-architecture/message/1598 Mute This Topic: https://lists.openembedded.org/mt/92611044/21656 Group Owner: openembedded-architecture+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
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 published by the project - also as an additional thought it would prevent situations where a hotfix needs to applied to older branches... Latest occurrences such as the github protocol issue or the backported override syntax makes me feel that issuing a warning might be not the best idea, even if the particular branch has not seen frequent updates. Still it would come down to either apply a commit to warn on every run or the mentioned datetime criteria - both of them can be tricked/avoided easily - so I don't see the benefit On 25.07.22 20:13, Alexander Kanavin wrote: 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 enough to ensure the message (of not using EOL yocto) reaches the users, and we need something better and directly seen by anyone invoking bitbake. Is it a terrible idea? Awesome idea? Ok-ish idea? Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1596): https://lists.openembedded.org/g/openembedded-architecture/message/1596 Mute This Topic: https://lists.openembedded.org/mt/92611044/21656 Group Owner: openembedded-architecture+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
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 it has crossed it? > > I feel that this page: > https://wiki.yoctoproject.org/wiki/Releases > is not enough to ensure the message (of not using EOL yocto) reaches > the users, and we need something better and directly seen by anyone > invoking bitbake. > > Is it a terrible idea? Awesome idea? Ok-ish idea? > I like the idea so users are aware of it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1594): https://lists.openembedded.org/g/openembedded-architecture/message/1594 Mute This Topic: https://lists.openembedded.org/mt/92611044/21656 Group Owner: openembedded-architecture+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[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 enough to ensure the message (of not using EOL yocto) reaches the users, and we need something better and directly seen by anyone invoking bitbake. Is it a terrible idea? Awesome idea? Ok-ish idea? Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1593): https://lists.openembedded.org/g/openembedded-architecture/message/1593 Mute This Topic: https://lists.openembedded.org/mt/92611044/21656 Group Owner: openembedded-architecture+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
