| Summary: |
RRS should display downgrade information in Updates history |
| Product: |
[Yocto Project Subprojects] Recipe Reporting System (RRS)
|
Reporter: |
Jose Lamego <jose.a.lamego> |
| Component: |
Recipe Reporting System (RRS) | Assignee: |
Paul Eggleton <bluelightning> |
| Status: |
IN PROGRESS REVIEW
---
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
randy.macleod, sgw, tim.orling
|
| Version: |
2.5 | |
|
| Target Milestone: |
6.99 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
| Attachments: |
|
Created attachment 4088 [details] screenshot from a downgraded recipe The updates history section in RRS does not include information regarding version downgrades, leading to confusion due to mismatching current version and latest update commit. A revert commit should be handled the same way as an update commit and include this information. For example: commit 2d238896de3dd946022eab4c447243bd33641a14 effectively downgraded flex to 2.6.0, but this is not reflected in the recipe's Upgrades history, where the latest entry points to an upgrade to 2.6.2 (screenshot attached)