In order to take advantage of new functionality we'd like to upgrade the OpenEmbedded patchwork instance at http://patchwork.openembedded.org/ using the fork available here: https://github.com/dlespiau/patchwork For more information see the proposal I made late last year on the mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113433.html
An upgraded version is up at http://patchwork-test.openembedded.org/ now and I am testing the patch state scripts on it. Since there are no releases for this fork I am running this commit from May 3: 2670f32dfd22dc4e60907b85365f48d47eb72456. Is this acceptable or do we need to routinely pull in new commits? I'd like help testing but I'm not sure what to ask for as I don't use Patchwork routinely. I can pull from the production database and re-run the upgrade by request. There are certainly a few missing patches because of missed e-mail. We are also potentially waiting for new hardware for the upgrade. I'm waiting to hear back about the need for that versus upgrading in place.
Status update: https://patchwork-next.openembedded.org/ is up and being tested. I'm still resolving performance issues. Once those are solved this version can replace http://patchwork.openembedded.org/ as all existing functionality is working. Some of the new functionality, such as series creation, is still being looked at. At this point I need help deciding on migrating the database from patchwork.oe.org to patchwork next again or not. It seems that that data in patchwork-next is still up to date with the current production version. Is that correct?
We've updated to the new patchwork version now so can resolve this.
Instance is up and running https://patchwork.openembedded.org/