If anyone has better info on workflow it would be great to help people figure it out. Ideally if we end up liking this tool it would be good to integrate it into the git workflow tool and ideally have some script to handle both the JIRA attachment and the review board.
This is great. So far I reviewed 2 patches using reviewboard and it is a huge time saver. I have one question about the setup though - the reviewboard has a Bugs field that takes in the JIRA, can it update the respective JIRA with the reviewboard link ? The concern is that with more reviews coming in through review board, it will soon become intractable since there is also no easy way to search by Bug in reviewboard.
On Mon, Aug 26, 2013 at 1:00 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:
Yeah the lack of integration is kind of maddening if you have ever used github.
My recommendation is that we treat Review Board as just a patch viewer and discussion tool. In other words you must have a JIRA and a link to the appropriate review board there. We should make no effort to use review board's dashboard or close the rbs or anything like that. I think it is reasonable to give the +1 in RB, though.
Thanks, Neha On Wed, Sep 11, 2013 at 11:28 AM, Tejas Patil <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext