Since patches are often batched into mut and can stay there a bit, depending, it would be good to track the whole life cycle of the patch so that the author knows where the patch is and what they should expect next. Silence is confusing :/
I think it's ross/mut in poky-contrib or master-next in the main poky repo depending on whether it's Ross or Richard assembling the branch, but I did see that Ross created a "mut2" branch the other day. If we're to be able to provide these status updates to submitters effectively, either we need to only have one nominated branch (or a clearly defined subset) or we have some other way of identifying these branches so that the tool can know where they are. Richard / Ross - any thoughts?
This enhancement requires further discussion due to the use of alternative branches and maybe new patch-statuses. Pushing to 2.4 to allow this.
We can add the desired additional branches to be monitored by patchwork's post-receive git hook, where the status updating takes place. What we would need prior to that, is to define which branches will be monitored and the related state name to be displayed at patchwork, for example, we could have "Under Test" for mut.
Its worth noting that the git hook uses the commit hash to identify the targeted patch to be updated, so if for any reason this hash changes between branches, the continuity will be broken.
These are the branches Ross suggested: master-next poky-contrib:ross/mut I propose that the states used in patchwork to reflect when a patch goes into one of them are (respectively): master-next mut Let me know if other branch is missing.
Change implemented at Open Embedded repositories for master and master-next branches. Pending implementation at Yocto repository for ross/mut branch only. Moving to M2 for finalization.
Change at Yocto repository has been queued and will implemented in M3. I'm moving this bug accordingly.
The Yocto-repository server configuration required for the ross/mut branch-tracking feature to be available is still in queue for implementation, although higher priority items are being handled before. I'm moving this request to the next enhancements-allowed milestone.
Created attachment 4138 [details] post-receive script
Following are the required changes that are queued to be implemented at the Yocto project's poky-contrib.git repository so the ross/mut branch can be tracked: - A local patchwork repository must be cloned from git://git.yoctoproject.org/patchwork (production branch) in order to have available the latest post-receive.hook and pwclient files - Create a local .pwclientrc file with same credentials as the one in OE's server. - Place the attached post-receive script (for example, in /home/git/bin and sym-linked from the poky-contrib.git repo), ensuring that the paths in the script are appropriate for the local configuration or edit them accordingly: "/home/git/repositories/poky-contrib.git" and "/usr/local/patchwork/tools/post-receive.hook"
Bulk move from 4.99 or 0.00 to 5.99