That is an excellent point which I forgot to call out: please do NOT try to use MozReview for confidential/security/nonpublic patches. MozReview will actually prevent you from publishing a review request linked to a nonpublic bug. Review Board does not have anything close to the fine-grained security model used by BMO; eventually we will support all our use cases, but this will require careful consideration and a lot more work in our Review Board extensions. For now, nonpublic patch should use old review system (Splinter). Apologies for the inconvenience.
Mark On 2014-11-10 6:31 AM, Gijs Kruitbosch wrote: > It looks like all reviews (and patches) are currently public. Is there > some way to have them not be so, for security/confidential bugs/reviews? > > ~ Gijs > > On 06/11/2014 04:50, Mark Côté wrote: >> A couple months ago I gave a sneak peak into our new repository-based >> code-review tool based on Review Board. I'm excited to announce that >> this tool, now named (descriptively but unimaginatively) MozReview, is >> ready for general use. >> >> In the interests of beta-testing our documentation at the same time as >> our code, I want to mostly confine my post to a link to our docs: >> http://mozilla-version-control-tools.readthedocs.org/en/latest/mozreview.html >> >> >> Everything you need should be in there. The only item I want to >> highlight here is that, yes, we know the UI is currently not great. We >> bolted some stuff onto the basic Review Board interface for our >> repository-centric work flow. We're working on integrating that into a >> whole new look & feel that will also strip out the bits that aren't as >> pertinent to our approach to code review. Please bear with us! We hope >> that, UI warts notwithstanding, you'll still enjoy this fresh approach >> to code review at Mozilla. >> >> Mark >> > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
