Hi Bruce, > On 24 Mar 2022, at 13:06, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > > > > On Thu, Mar 24, 2022 at 4:42 AM Bertrand Marquis <bertrand.marq...@arm.com> > wrote: > Hi, > > > On 23 Mar 2022, at 22:17, Bruce Ashfield via lists.yoctoproject.org > > <bruce.ashfield=gmail....@lists.yoctoproject.org> wrote: > > > > > > > > On Wed, Mar 23, 2022 at 6:30 AM Richard Purdie > > <richard.pur...@linuxfoundation.org> wrote: > > On Wed, 2022-03-23 at 08:38 +0000, Bertrand Marquis wrote: > > > Hi Paulo > > > > > > > On 22 Mar 2022, at 16:52, Paulo Sherring via lists.yoctoproject.org > > > > <pauloasherring=gmail....@lists.yoctoproject.org> wrote: > > > > > > > > Hello Diego, Bertrand, > > > > Just confirmed that by bringing these changes into hardknott, the > > > > modules get correctly probed on bootup. > > > > > > Great thanks for the info. > > > > > > @Bruce: Maybe it would make sense to backport this as hardknott is LTS ? > > > If yes, please ping me if you need support to do it. > > > > hardknott is not LTS, it is about to go EOL. > > > > > > Agreed. I don't like to leave things broken either .. but we really > > shouldn't encourage people to keep using the branches that are going out of > > support. If I fix this one, there will be other issues that aren't > > fixed/patched in the future (and potentially security issues) .. so I'm > > leaning towards leaving this not backported. > > The branch is still supported at the moment and is broken. > I do not think it is right to say “we will stop fixing issues a bit before > the branch is out of support” as this is equivalent to reducing the support > time. > Out of support is more something which should be works but does not get any > update or security fixes, here we have something broken while under support. > > > Broken is a far too dramatic description of this issue. > > Also, when talking about support, we are talking about OEcore / Yocto Project > support. The rest of the layers in the ecosystem do this sort of support as > best effort. So a gentle reminder that we should all be careful with > expectations and the tone of our communications. >
Sorry if my tone did not sound right, that was not my intention. I just wanted to understand what we should expect and hence what we should do in stable branches. > > Anyway the fix is simple and the person is unblocked so it will be easy for > the next one to solve it, so my argumentation is more in general around what > should the end of support date mean for users. > > I have queued the change, but my reminder about expectations stands. Thanks. I think that would be good to be clear on what can be expected in a stable branch after the release for meta-virtualization. That could also help me to know what I should consider critical ornate and fix in stable releases. Kind regards Bertrand > > Bruce > > > > Cheers > Bertrand > > > > > Bruce > > > > > > https://wiki.yoctoproject.org/wiki/Releases > > > > Cheers, > > > > Richard > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await thee > > at its end > > - "Use the force Harry" - Gandalf, Star Trek II > > > > > > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await thee at > its end > - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#7116): https://lists.yoctoproject.org/g/meta-virtualization/message/7116 Mute This Topic: https://lists.yoctoproject.org/mt/89949013/21656 Group Owner: meta-virtualization+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
