8704 2015-11-18 22:21:22 +0000 patchwork: support history tracking of patch status 2017-12-06 16:51:09 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork unspecified All Multiple RESOLVED FIXED Medium+ enhancement 2.2 M1 9130 1 bluelightning jose.a.lamego damien.lespiau jose.perez.carranza --- --- No (bug/feature does not impact docs) oldest_to_newest 56604 0 bluelightning 2015-11-18 22:21:22 +0000 Support tracking changes to the status of a patch in patchwork (so there is an audit trail of who changed the status and when, where "who" might also be an automated script). It's possible this functionality already exists upstream, I'm not sure. 56983 1 damien.lespiau 2015-12-03 11:37:55 +0000 The history of patches states isn't kept at the moment. This could be done with https://github.com/dlespiau/patchwork/issues/40 58315 2 jose.a.lamego 2016-01-28 18:21:40 +0000 Updating target milestone. Fix development will be carried on, but final implementation will depend on Patchwork version update. 58677 3 jose.a.lamego 2016-02-05 18:17:55 +0000 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 59591 4 jose.a.lamego 2016-03-01 15:45:19 +0000 Pull Request v2 sent to upstream. 59902 5 jose.a.lamego 2016-03-11 15:57:27 +0000 Change merged in upstream. Waiting for the OE Patchwork to be updated to latest version for the feature to be available to all users. 63348 6 jose.a.lamego 2016-06-27 17:27:58 +0000 Updating target milestone to match that of Dependency 63735 7 jose.a.lamego 2016-07-07 15:36:38 +0000 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