On Fri, Jun 22, 2012 at 2:57 AM, Jenny Hong wrote:
> Hi Robert,
>
> Sorry, I was a little unclear with my first question; I meant that we need
> to do separate reviews for each project. Is there some way to submit a
> single review that covers multiple projects?
Not at the moment, there isn't.
>
Hi,
I'm a little confused about what you mean by revision sets. Are you
referring to SVN or Mercurial? When searching around for tagging local
revision sets, I found many results regarding Mercurial.
My understanding of tagging is that the eventual merging, after the
reviews, is slow and expen
You can tag local revision sets of your changes in Eclipse thereby creating
a reference point to diff against. By combining that with subversion
revision numbers or labels you should be able you get what I think you're
describing.
On Jun 21, 2012 6:57 PM, "Jenny Hong" wrote:
> Hi Robert,
>
> Sorr
Hi Robert,
Sorry, I was a little unclear with my first question; I meant that we need
to do separate reviews for each project. Is there some way to submit a
single review that covers multiple projects?
With regard to the workflow, there are a few options, but all of them have
significant prob
Hi Jenny,
On Thursday, June 21, 2012 8:47:11 PM UTC+3, Jenny Hong wrote:
>
> How are people dealing with the workflow in the ReviewBoard plug-in for
> Eclipse? Some problems we are encountering are
>
>- doing separate posts for every review
>
> How would you propose streamlining the process o
How are people dealing with the workflow in the ReviewBoard plug-in for
Eclipse? Some problems we are encountering are
- doing separate posts for every review
- changing workspaces to do pre-commit code reviews, which are expensive.
Thanks!
--
Want to help the Review Board project? Donat
