Critical fixes may need to be implemented in OE Patchwork much sooner than when they get merged to upstream. For this to safely take place, a staging instance is needed where the changes can be tested using production data/hardware before going live. The new staging instance must use code from a repository alternate to upstream at: https://github.com/joselamego/patchwork.git using the branch "oe-staging"
The new staging instance must also receive patches from the mailing list just the same as in production.
Michael, do you have an ETA for this?
Wednesday Aug 31st should be possible.
Any updates on this?
This will be ready tomorrow.
Separate Patchwork staging instance is up at https://patchwork-staging.openembedded.org/ synced with production as of this morning.
(In reply to comment #6) > Separate Patchwork staging instance is up at > https://patchwork-staging.openembedded.org/ synced with production as of > this morning. Wasn't it supposed to track "oe-staging" from joses repo -- or is that something Jose can do?
(In reply to comment #7) > (In reply to comment #6) > > Separate Patchwork staging instance is up at > > https://patchwork-staging.openembedded.org/ synced with production as of > > this morning. > > Wasn't it supposed to track "oe-staging" from joses repo -- or is that > something Jose can do? patchwork-staging is pointing to my repo and currently receiving patches from the mailing list only for Open Embedded Core Layer project. I am verifying the implemented fixes, which seem to be working as expected, with one exception: I may have to reopen 9941 (most likely due to an OE server configuration since issue is not reproducible in other instances) and track work in that bug.