Bug 8162

Summary: patchwork: clear out the superseded and already merged patches
Product: [Yocto Project Subprojects] Patchwork/Patchtest Reporter: Paul Eggleton <bluelightning>
Component: PatchworkAssignee: Michael Halstead <mhalstead>
Status: RESOLVED FIXED QA Contact: Alexandru Georgescu <alexandru.c.georgescu>
Severity: enhancement    
Priority: Medium+ CC: benjamin.esquivel, damien.lespiau, leonardo.sandoval.gonzalez
Version: unspecified   
Target Milestone: 2.2 M4   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Scripts to update merged and superseded patches in Patchwork backlog
none
Scripts to update merged and superseded in Patchwork backlog none

Description Paul Eggleton 2015-08-14 16:47:40 UTC
It would be nice if in the bitbake and oe-core projects in the OE patchwork instance that we could go through the backlog of patches and set the status for the superseded and already merged ones appropriately using a script, so we'd be left with just the ones that are unmerged or were rejected.
Comment 1 Damien Lespiau 2015-10-26 16:26:01 UTC
Corresponding issue in github:

  http://github.com/dlespiau/patchwork/issues/61
Comment 2 Jose Lamego 2016-01-28 18:18:42 UTC
Updating target milestone. Fix code is currently under peer review.
Comment 3 Jose Lamego 2016-02-12 18:37:40 UTC
Created attachment 2979 [details]
Scripts to update merged and superseded patches in Patchwork backlog
Comment 4 Jose Lamego 2016-02-12 18:40:52 UTC
A script was developed to update to Accepted state the already merged patches and a second script to update to Superseded the patches that are in New state and include the same subject as other patches with an upper version prefix and in Accepted state. An individual log file will be created for each.

These scripts should only be executed once to clean up the backlog and would not be required afterwards since Patchwork is now automatically updating the merged patches and will also update the superseded once its updated to the latest code.
Comment 5 Jose Lamego 2016-03-03 22:04:00 UTC
Developed scripts were sent to admin for deployment at first opportunity.
Comment 6 Benjamin Esquivel 2016-03-03 22:25:31 UTC
I would not mark this as completed until the deployment has finished, instead, I'd put it as NEEDINFO and assign it to the person who will deploy such scripts.
Comment 7 Jose Lamego 2016-03-03 22:28:32 UTC
Reopening to wait for implementation to be completed.
Comment 8 Jose Lamego 2016-03-03 22:31:41 UTC
Michael, please let me know when these scripts are executed.
Comment 9 Michael Halstead 2016-04-28 17:19:33 UTC
After testing and a meeting between Paul and Jose this is postponed until after the patchwork upgrade.
Comment 10 Michael Halstead 2016-06-29 16:55:16 UTC
At this point we are running patchwork-update-commits as part of the patchwork upgrade and are not running update_superseded_commits at all.

Jose I'm going to give this back to you until we have a new version of update_superseded_commits to try.
Comment 11 Jose Lamego 2016-09-01 02:11:03 UTC
Created attachment 3402 [details]
Scripts to update merged and superseded in Patchwork backlog

Update Supersed patches script must be executed in a machine with both Python2 and Python3 available to avoid ascii/unicode decoding errors.
Comment 12 Jose Lamego 2016-09-08 19:32:12 UTC
Michael, please let me know when the Update Superseded Patches script is executed and provide me a copy of the created log for further analysis.
Comment 13 Michael Halstead 2016-10-06 00:29:47 UTC
These scripts have completed. 

Jose, please find the log in e-mail.