| Summary: | patchwork: support history tracking of patch status | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Paul Eggleton <bluelightning> |
| Component: | Patchwork | Assignee: | Jose Lamego <jose.a.lamego> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | damien.lespiau, jose.perez.carranza |
| Version: | unspecified | ||
| Target Milestone: | 2.2 M1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 9130 | ||
| Bug Blocks: | |||
|
Description
Paul Eggleton
2015-11-18 22:21:22 UTC
The history of patches states isn't kept at the moment. This could be done with https://github.com/dlespiau/patchwork/issues/40 Updating target milestone. Fix development will be carried on, but final implementation will depend on Patchwork version update. Pull request sent to upstream [1]. If approved, this change will be implemented in production when upgrading Patchwork version. [1] https://github.com/dlespiau/patchwork/pull/140 Pull Request v2 sent to upstream. Change merged in upstream. Waiting for the OE Patchwork to be updated to latest version for the feature to be available to all users. Updating target milestone to match that of Dependency Patch status is now tracked in the log for "state-change-event" event. For example: https://patchwork.openembedded.org/api/1.0/projects/5/events/?name=patch-state-change |