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: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
