<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Opera Husband &#187; Trac</title>
	<atom:link href="http://blog.tmacsoft.com/category/trac/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.tmacsoft.com</link>
	<description>Saving the world, one soprano at a time</description>
	<lastBuildDate>Thu, 24 Jun 2010 17:20:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>More Code Review Tools</title>
		<link>http://blog.tmacsoft.com/subversion/more-code-review-tools</link>
		<comments>http://blog.tmacsoft.com/subversion/more-code-review-tools#comments</comments>
		<pubDate>Sun, 07 Oct 2007 20:12:04 +0000</pubDate>
		<dc:creator>tom</dc:creator>
				<category><![CDATA[Code Review]]></category>
		<category><![CDATA[Subversion]]></category>
		<category><![CDATA[Trac]]></category>

		<guid isPermaLink="false">http://blog.tmacsoft.com/svn/more-code-review-tools</guid>
		<description><![CDATA[A couple more code review tools to consider
ReviewBoard
Crucible  Works with Fisheye
Code Collaborator
Google Mondrian

Peer Review Plugin for Trac
Note the Trac Hacks site http://trac-hacks.org/wiki/PeerReviewPlugin is down for awhile.
jian cha
Next step is to get some work-flow setup.  Possibly with Subversion so we know what code has been reviewed and ready for release.  We also need [...]]]></description>
			<content:encoded><![CDATA[<p>A couple more code review tools to consider</p>
<p><a href="http://code.google.com/p/reviewboard/">ReviewBoard</a></p>
<p><a href="http://www.atlassian.com/software/crucible/">Crucible</a>  Works with <a href="http://www.atlassian.com/software/fisheye/">Fisheye</a></p>
<p><a href="http://smartbear.com/codecollab.php">Code Collaborator</a></p>
<p><a href="http://video.google.com/videoplay?docid=-8502904076440714866">Google Mondrian</a></p>
<p><a href="https://trachacks.coderanger.net/wiki/PeerReviewPlugin"><br />
Peer Review Plugin for Trac</a><br />
Note the Trac Hacks site http://trac-hacks.org/wiki/PeerReviewPlugin is down for awhile.</p>
<p><a href="http://www.blisted.org/wiki/projects/JianCha">jian cha</a></p>
<p>Next step is to get some work-flow setup.  Possibly with Subversion so we know what code has been reviewed and ready for release.  We also need to decide on whether the reviews happen pre or post commit.  Ideally the change log and release notes would include links to the reviews.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=More+Code+Review+Tools+http://onn6p.th8.us" title="Post to Twitter"><img class="nothumb" src="http://blog.tmacsoft.com/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=More+Code+Review+Tools+http://onn6p.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://blog.tmacsoft.com/subversion/more-code-review-tools/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
