9130 2016-02-17 20:02:04 +0000 Update OE patchwork instance 2016-07-29 17:22:20 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork unspecified x86 Multiple VERIFIED FIXED High enhancement 2.2 M1 7684 8714 8715 4078 7654 7656 7658 8442 8648 8649 8704 8716 8717 1 bluelightning mhalstead jose.perez.carranza richard.purdie jose.perez.carranza --- --- No (bug/feature does not impact docs) oldest_to_newest 59165 0 bluelightning 2016-02-17 20:02:04 +0000 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 62128 1 mhalstead 2016-05-11 21:01:47 +0000 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. 63478 2 mhalstead 2016-06-29 17:02:48 +0000 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? 63725 3 richard.purdie 2016-07-07 15:01:49 +0000 We've updated to the new patchwork version now so can resolve this. 64671 4 jose.perez.carranza 2016-07-29 17:22:20 +0000 Instance is up and running https://patchwork.openembedded.org/