Bug 14642 - Yocto-check-layer add patch Upstream-Status check
Summary: Yocto-check-layer add patch Upstream-Status check
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 4.2 M3
Assignee: Chee Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-12-03 17:44 UTC by akuster
Modified: 2023-03-14 08:20 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description akuster 2021-12-03 17:44:40 UTC

    
Comment 1 Richard Purdie 2021-12-05 12:33:01 UTC
Should the compatibility status mandate some percentage of patches are not in Pending state? The later checks could at least report the percentage of patches in pending state?
Comment 2 akuster 2021-12-11 13:59:27 UTC
(In reply to comment #1)
> Should the compatibility status mandate some percentage of patches are not
> in Pending state? The later checks could at least report the percentage of
> patches in pending state?

I hadn't thought to that level of details.

yes, I think a percent of patches with no 'Upsteam-Status" and with status may be a good first step.

I am not sure about mandating a percentage. I am thinking of a BSP layer with an EOL kernel having patches that have no where to go but a form of the patch may have been accepted in a later.  I think its more important to have the data to allow a deep dive into the areas of concern.
Comment 3 akuster 2021-12-16 15:58:07 UTC
Having an "Upstream-Status" in patches is being considered an additional Yocto Compatible requirement.
Comment 4 Chee Yang 2023-02-27 06:56:44 UTC
This added check for Upstream-Status.
https://git.yoctoproject.org/poky/commit/?id=80a2028813d3c861f3aea0d7f5e91d9cccb7d689
Comment 5 Richard Purdie 2023-03-14 08:20:17 UTC
Since we now show the warnings in yocto-check-layer, I think we can resolve this, thanks for the patch!