Permissions on requests draft

2011-12-15 Thread Manuel
Hello,

First of all, thanks for ReviewBoard we are using it for reviewing
Tuleap development since a couple of weeks and it's really helpful!

We are trying to do this (based on RB 1.6):
- Our model is: post-reviews on development branches before merge into
trunk (subversion)
- A group of fellow contributors are able to create new review
requests
- They are doing a first round of review internally and when they are
proud of their code, they ask for review to core developers. So we
created 2 review groups (tuleap-contrib and tuleap-core).
- But when one -contrib member created a review for a given branch,
others cannot update the review.
- Typical scenario:
* Developer A submit a first review request
* Integrator K make some comments
* Developer B does some fix, update the diff, answers comments but is
not allowed tu publish this draft. He has to wait for Developer A to
update the diff.

I don't know if it's clear enough.

Is there any way to get all the members of one group to update the
reviews of its siblings ?

Thanks,
Manuel

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en


Re: Issues with RBTools and Subversion

2011-12-15 Thread Charlie Hsu
svn 1.7's diff returns some extra entries for added binary files (the
prop-add).

We've been getting around this by parsing the diff, keeping track of
any files marked as a binary type, and deleting any subsequent Index:
FILE entries where FILE is one of those binary files. So for example,
changing your diff to just the entry below should make it work...

Index: run/assets/x
===
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream


Charlie

On Nov 18, 12:48 pm, Jeff Ward j...@fuzzybinary.com wrote:
 Hey All,

 I'm having some problems with Subversion 1.7 and RBTools.  It looks
 like Subversion 1.7 (at least SilkSvn) broke using Windows GNU Diff,
 using --diff-cmd as all attempts to get the diff error out with:
 ===
 svn: E200012: 'diff' returned 2
 svn: E175002: Error reading spooled REPORT request response

 This is probably a bug in subversion 1.7, but I can't get around it
 (unless someone knows a good way to do this?)

 So I wrote a script to take care of some of this by manually
 generating the diff from svn and handing that to RBTools directly.
 Now however, I'm getting a different issue.  When we added a new
 binary file, SVN's diff says:
 Index: run/assets/x
 ===
 Cannot display: file marked as a binary type.
 svn:mime-type = application/octet-stream
 Index: run/assets/x
 ===
 --- run/assets/x    (revision 184)
 +++ run/assets/x    (revision 185)

 Apparently when this gets sent to Review board, it makes it unhappy
 and reports this:

  Got API Error 207 (HTTP code 400): The file was not found in the 
  repository
  Error data: {u'stat': u'fail', u'file': u'/run/assets/x', u'err': 
  {u'msg': u'The file was not found in the repository', u'code': 207}, 
  u'revision': u'184'}

 Is there a way around this?  Should Review board understand that
 revision --- for revision 184 means it *shouldn't* exist?

 --
 Jeff

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en


Re: Issue 2422 in reviewboard: Sending mail failure

2011-12-15 Thread reviewboard


Comment #2 on issue 2422 by w.sitni...@gmail.com: Sending mail failure
http://code.google.com/p/reviewboard/issues/detail?id=2422

I use damn gmail SMTP

Settings were
server: smtp.gmail.com
port: 465
TSL enabled


after searching solution on google via 'reviewboard gmail smtp' I found  
this link

http://www.mail-archive.com/reviewboard@googlegroups.com/msg02778.html

which says that 465 port is bad , 587 is good. I tried and I got it working.

Thank you very much, close this please

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 2020 in reviewboard: User account page should list fish trophies acquired by the user.

2011-12-15 Thread reviewboard


Comment #1 on issue 2020 by nickthec...@gmail.com: User account page should  
list fish trophies acquired by the user.

http://code.google.com/p/reviewboard/issues/detail?id=2020

I agree. One should be able to lord one's trophies over one's colleagues.  
Otherwise, what's the point? :)


--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 2402 in reviewboard: RBTools 0.3.4 breaks HTTP authentication on Review Board 1.0

2011-12-15 Thread reviewboard


Comment #1 on issue 2402 by mkot...@gmail.com: RBTools 0.3.4 breaks HTTP  
authentication on Review Board 1.0

http://code.google.com/p/reviewboard/issues/detail?id=2402

I also experience the same issue on Linux RedHat 2.6 i686.

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.