Before completely decommissioning MozReview, we need to migrate the data somewhere. So far we have two broad ideas: * Upload patches to S3 and update attachment links to point there. * Upload patches to Bugzilla directly. In both cases we'd also want to update links in review comments.
(In reply to Mark Côté [:mcote] from comment #0) > Before completely decommissioning MozReview, we need to migrate the data > somewhere. So far we have two broad ideas: > > * Upload patches to S3 and update attachment links to point there. > * Upload patches to Bugzilla directly. All of the patches should already be in the review repository, it could just be made readonly?
Can we load every review request URL in a browser, take a snapshot of the finalized HTML, possibly remove references to JS, and upload a static HTML snapshot to S3? That way we'd get the full site content and layout without having to run a dynamic server. That's a bit of complexity. But it avoids having to re-normalize the data to Bugzilla. Pick your poison.
See the project planning doc linked in the URL field for planning details.
One of the current capabilities of MozReview is that you can pull the patches in a review request (including a historical one) into your local repository. This is possible because behind the scenes, MozReview knows all the ancestors of the patches submitted for review, including the ones that are not part of the review request. Will this ability be preserved by the archival process?
We are still working out proposals. Final decision on a process is a little ways off.
Comment on attachment 8959699 [details] Add a MozReview-to-Phabricator migration guide Mark Côté [:mcote] has approved the revision. https://phabricator.services.mozilla.com/D744
Attachment #8959699 - Flags: review+
This was announced last week (and the plan slightly amended afterward): https://groups.google.com/forum/?pli=1#!topic/mozilla.dev.platform/Bxomd5VAgKU
Status: NEW → RESOLVED
Last Resolved: 16 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.