Review Board 1.0 Released!

Review Board 1.0

Tonight, we hit a milestone in the Review Board project that we’ve been working toward for over two years. We finally pushed out our 1.0 release. A lot of blood, sweat and tears went into this release (okay, so not literally, but it was A LOT OF WORK!). The last few months in particular have been challenging, as we’ve had to solve some tricky bugs and scalability problems, but the end result is pretty great.

Just a short while ago, we announced the release and put up an overview of the entire release and product. We’ve already had some nice congratulatory e-mails and tweets, which is really nice 🙂

Some stats for this release:

  • 2 years, 9 months, 25 days have passed since our first commit.
  • 120 contributors have contributed to Review Board so far (in terms of code contributions).
  • 2,019 commits were made.
  • 899 review requests have been posted to our project’s actual Review Board server. 1,650 users are registered on there.
  • Our demo server, in comparison, has 2,082 review requests filed and 10,154 users.
  • 938 bugs were filed. 812 were fixed.
  • 232 feature requests were filed. 101 were implemented. Most remaining ones are scheduled for releases.
  • An estimated 200+ companies are now using Review Board. 26 have let us list them publicly.
  • The largest known Review Board install has over 83,000 filed review requests and over 2,000 users, doing upwards of 10GB of traffic per day.
  • 5 presentations on Review Board are known to have been given, 3 by us, 2 by others.
  • 552 users have joined our main mailing list, and 3,674 e-mails have been sent.

Now that Review Board 1.0 is out, we can get started on some awesome new features we’ve had planned. I have a little notebook full of ideas for our 1.1 and 1.5 releases (which may become 1.5 and 2.0, respectively, as this list grows). Some of the new features are actually ready to be committed within the next couple of days, so those of you using nightlies will start to see them soon.

We were accepted into this year’s Summer of Code, and have three students working on exciting projects for us, so hopefully we’ll start to see these trickle into the upcoming nightlies as well. Among these projects include diff viewer improvements (moved region detection, better whitespace-only change detection), IDE integration with Eclipse, and improved notification hooks and e-mail support.

We’re also working on providing support for third-party extensions, which will allow developers to extend Review Board in new, exciting ways without having to modify Review Board itself. This is especially handy for companies who wish to integrate better with their sandboxes, bug trackers or unit testing services. This will likely land in 1.5 (2.0?) at the earliest, as it’s a large change, but the code for this mostly works today. It’s just a matter of getting the codebase ready and figuring out what APIs we want to stabilize and expose.

As I mentioned in the release announcement, we’re planning a release party, tentatively on July 11th, 2009, in the Bay Area (somewhere around Palo Alto, CA). If any Review Board users want to join us, please RSVP!

13 thoughts on “Review Board 1.0 Released!

  1. Pingback: Dev Blog AF83 » Blog Archive » Veille technologique : Microsoft, Organisation, Ruby, Rails, PHP, Langages, Sécurité

  2. Great work on RB! It’s really great. In my opinion its more user friendly than SmartBear’s CodeCollaborator.

    Integration options for other SCM would be awesome. We’re waiting for the Vault/VSS integration. Is there any ETA on that?

    Thanks,
    JD

  3. JD: Thanks!

    People have talked about writing support. For many SCMs (especially Windows-based or for-cost SCMs) we pretty much rely on third parties to provide support. Fortunately this is easy, so long as there’s a command line tool or Python-enabled API for talking to the repository. We’d be glad to work with people on this.

    • JD: I’d e-mail the mailing list, see if other people are working on this, and then look into our existing reviewboard/scmtools/*.py files to get a feel for how you’d need to implement this. SCM support isn’t *too* complex, though I wouldn’t say it’s trivial either.

  4. You guys are rocking there. I am wondering why does the demo server have more registered users 😉 Summer of code should be exciting, let see if you come out of 1.1 quickly.

    I think you guys should just have hooks for SCMs and allow anyone to integrate their SCM. Most SCM can be configured to insist on ‘reviews’ before a commit is made.

  5. Well done, sir (and to everybody who worked on this). Reviewboard has been a high quality product for quite some time now; I’ve been enjoying watching it develop.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s