We currently only attempt to map each review/commit series to a single bug.
We will support multiple bugs eventually. Single bugs were easy to implement :) There is also an open bug to support specifying the base revision to review. Right now everything on the stack gets reviewed. That should hopefully get resolved this week. Keep the version-control-tools repo up to date. > On Nov 9, 2014, at 17:25, Blair McBride <bmcbr...@mozilla.com> wrote: > > It's quite common for me to be working on a bug that depends on another bug > that hasn't landed yet. I'm struggling to figure out how to make this work > with MozReview, since everything is lumped into one review group and > associated with one bug. > > ie, I have: > * Bug 1 - patch A (this is either waiting for review, or hasn't landed on m-c > yet) > * Bug 2 - patch B (I want to put this up for review) > > If I push this to reviewboard, both patches get automatically grouped > together and associated with Bug 1. I can specify --reviewid to make them get > associated with Bug 2, but that also puts Bug 1's patch in Bug 2. > > (Note that I'm using MQ, because I can't figure out how to do this via > bookmarks either.) > > - Blair > > > > Gijs Kruitbosch wrote: >> All of hg.m.o is currently 503 >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1094922 >> >> ~ Gijs >> >>> On 06/11/2014 16:58, Benoit Girard wrote: >>> Cool. I'm eager to try this out. Sadly >>> https://hg.mozilla.org/hgcustom/version-control-tools is giving me a >>> 503 error at this time. >>> >>>> On Wed, Nov 5, 2014 at 11:50 PM, Mark Côté <mc...@mozilla.com> 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 >> >> _______________________________________________ >> 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 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
