Difference between revisions of "Code Review Tool"

Revision as of 14:16, 6 July 2017

At one time, Linden Lab maintained an instance of the ReviewBoard code review tool at codereview.secondlife.com to be used for reviewing proposed changes to any of our open source projects. That system has been retired in favor of using the review features integrated into Bitbucket.

The content of reviews on that system is available in this archive.

@@ Line 1: / Line 1: @@
-{{RightToc}}
+{{Project Snowstorm Nav}}
+At one time, Linden Lab maintained an instance of the [http://www.reviewboard.org/ ReviewBoard] code review tool at codereview.secondlife.com to be used for reviewing proposed changes to any of our open source projects. That system has been retired in favor of using the review features integrated into Bitbucket.
-:''Given enough eyeballs, all bugs are shallow''
+The content of reviews on that system is available in [http://lecs-opensource.secondlife.com/codereview.secondlife.com/r/index.html this archive].
-:: - [http://en.wikipedia.org/wiki/Linus%27_Law Linus' Law], according to Eric S. Raymond
-Linden Lab maintains an instance of the [http://www.reviewboard.org/ ReviewBoard] code review tool at [https://codereview.secondlife.com codereview.secondlife.com] to be used for reviewing any proposed changes to any of our open source projects.
-Use of this system is limited to developers who have executed a [http://lecs.opensource.secondlife.com/SLVcontribution_agmt.pdf Second Life Viewer Contribution Agreement].  Any changes or comments posted to the tool are Contributions as defined by that Agreement.
-==Logging In==
-Access to the system requires that you set up an account, which you can do on your own from the login page
-or by going directly to the [https://codereview.secondlife.com/account/register/ account registration page].
-When creating your account:
-* Please use the same user id that you use for Jira.
-* Use the same email address that you use for the opensource-dev mailing list (if you do not, then the notices of reviews you post and comments you make will not be successfully sent to the list).
-* Select the 'Viewer' group
-==Post Code To Be Reviewed==
-Prepare your change in a local working hg repository.  It will be easier to keep track of outstanding reviews if you commit your change to that repository before posting it for review.
-Once you have a local copy of the change, there are two ways to post it for review:
-* [[#Manual Upload|Manual Upload]] using the web page interface
-* [[#post-review|post-review]] command line tool
-Either way, you must [[#Publish Your Review|Publish Your Review]] before any other users will be able to see it or comment on it.
-===Manual Upload===
-To create a patch file that shows your change, execute the following command from the top level of your repository:
- hg diff -r ''commit'' > PATCH
-where ''commit'' is the revision identifier for your change (if you have not made any other changes, this can just be <tt>tip</tt>).  If you have not committed your change, you can leave off the <tt>-r ''commit''</tt>, but this is not recommended.
-===post-review===
-There is a command line tool called '''post-review''', but it is not very mature and whether or not it works can depend on how you created your mercurial repository.   ''I plan to work on improving this asap - Oz''
-===Publish Your Review===
-==Commenting==
-Whenever possible, comment by selecting lines in the file and entering a comment.  It makes it much more specific than if you post a general comment.

Difference between revisions of "Code Review Tool"

Revision as of 14:16, 6 July 2017

Navigation menu

Search