> -----Original Message----- > From: Richard Purdie <richard.pur...@linuxfoundation.org> > Sent: Thursday, February 23, 2023 9:49 PM > To: Bruce Ashfield <bruce.ashfi...@gmail.com>; Lee, Chee Yang > <chee.yang....@intel.com> > Cc: openembedded-core@lists.openembedded.org > Subject: Re: [OE-core] [PATCH] checklayer: check for patch file upstream > status > > On Thu, 2023-02-23 at 08:33 -0500, Bruce Ashfield wrote: > > I don't recall the upstream-status being added as a yocto > > compatibility requirement. Can someone point me to a discussion that I > > missed ? > > It isn't a requirement at this time and there isn't any recent discussion > you've > missed.
Sorry that I misunderstand the discussion in the bug ticket. Would update the commit message to avoid confusion. > > The topic has come up now and again at various points, including with the YP > TSC and I suspect that was why we have > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14642 from back in 2021. I > think the view of the YP TSC was that we probably should warn about things > like this from yocto-check-layer perspective as it is a best practise we want > to > raise the profile of. > > > As everyone can recall, I wasn't on board with this being a default QA > > check and error, and I'm also not on board with it being a yocto > > compliance error. > > > > I realize it isn't being made an error in this patch, but I wanted to > > raise my concerns now, before someone throws that switch. > > Your concerns are definitely known! As I said at the time in the discussion, > the TSC does intend to add some extra checks around QA issues to YP > Compatible but no decision on which ones has been made yet, I think that > action rests with me to make a proposal. My view is this one can remain a > warning, I can't speak for the rest of the TSC. I do think having yocto-check- > layer show more warnings about best practises if the direction things will > move though even if it doesn't change the resulting compatibility status. > > There is an intent to improve "quality" over time so I can't promise this will > never become an error but I don't have any plans to push this beyond a > warning. As above, I can't speak for all TSC members though. > > Cheers, > > Richard > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177647): https://lists.openembedded.org/g/openembedded-core/message/177647 Mute This Topic: https://lists.openembedded.org/mt/97178225/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
