The problem there is that the review repo will be bundled and stored. We don't want to run another Mercurial server indefinitely. Although, if the parent is a public changeset (as I believe most are), we could put a link to that commit in mozilla-central somewhere.
Mark On Thu, Jul 26, 2018 at 5:55 PM, Karl Tomlinson <mozn...@karlt.net> wrote: > Mark Côté writes: > > > On August 20, we will remove public access to MozReview and archive > > patches. Every landed, in-progress, and abandoned patch will be > downloaded > > from MozReview and stored in an S3 bucket. The “stub attachments” in > > Bugzilla that currently redirect to MozReview will be updated to link to > > the appropriate S3 bucket. Review flags and bug comments will be > preserved. > > > We will also be writing a simple redirection service to map specific > > MozReview reviews to associated BMO comments, review requests to > associated > > bugs, and review-request diffs to the appropriate S3 buckets. > > Could the stub attachments and review-request diffs (but not > interdiffs of course) redirect to the commits in the review repo > (at https://reviewboard-hg.mozilla.org/gecko/ or wherever this > ends up), please? > > The parent revision is important to the meaning of a patch, and > it is not clear that navigation from the S3 buckets to the > mercurial revisions in the review repo will be easy. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
