Issue 2867 in reviewboard: allow reporter to resolve issues

2013-01-16 Thread reviewboard
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2867 by matthew@kitware.com: allow reporter to resolve issues http://code.google.com/p/reviewboard/issues/detail?id=2867 What version are you running? RB 1.7.1 What's the URL of the page this enhancement relates to,

Issue 2868 in reviewboard: allow closing issues when updating request

2013-01-16 Thread reviewboard
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2868 by matthew@kitware.com: allow closing issues when updating request http://code.google.com/p/reviewboard/issues/detail?id=2868 What version are you running? RB 1.7.1 What's the URL of the page this

Re: Issue 2860 in reviewboard: GCC_4.2.0 version not found

2013-01-16 Thread reviewboard
Comment #3 on issue 2860 by chip...@gmail.com: GCC_4.2.0 version not found http://code.google.com/p/reviewboard/issues/detail?id=2860 If it's not showing up in the reviewboard.log, then we don't have any additional logging that would help here. It can occur at many points, though. The one

Re: Issue 2713 in reviewboard: Reviewer, not author, should mark issues as resolved/reopened

2013-01-16 Thread reviewboard
Comment #5 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 Issue 2867 has been merged into this issue. -- You received this message because you are subscribed to the Google Groups

Re: Issue 2867 in reviewboard: allow reporter to resolve issues

2013-01-16 Thread reviewboard
Updates: Status: Duplicate Mergedinto: 2713 Comment #1 on issue 2867 by trowb...@gmail.com: allow reporter to resolve issues http://code.google.com/p/reviewboard/issues/detail?id=2867 (No comment was entered for this change.) -- You received this message because you are

Re: Issue 2713 in reviewboard: Reviewer, not author, should mark issues as resolved/reopened

2013-01-16 Thread reviewboard
Comment #6 on issue 2713 by matthew@kitware.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 A three-stage flow would work. It's a little inconvenient (and also odd) for the author to not be able to indicate