Review Board 2.0.14 is out!

We've been busy squashing Review Board bugs left and right, all in preparation for Review Board 2.0.14, which is out... now.

There are a bunch of bugs fixed throughout the diff viewer, making the experience of viewing diffs a bit better. We've also fixed some major API caching issues from 2.0.13 that manifested in different ways (so if you're running that release, definitely upgrade).

Review Board 2.0.14 was designed to work with the newly-released RBTools 0.7.2. With their powers combined, you'll have a faster, more reliable experience with many of the RBTools commands, and when coding against the RBTools API.

This release depends on Django 1.6.10, which includes a number of security improvements you probably want. A good reason to upgrade by itself.

There are lots of other fixes and improvements in this release. See the release notes for the full list.

RBTools 0.7.2 is here!

It's been just over a month since RBTools 0.7.1 arrived at stores near you (or probably not). That's a whole month spent not upgrading RBTools, and we can't have that. Plus, there were some good bug fixes and new commands we thought we'd send your way. So let's not waste any more time. Here's what's in today's release of RBTools 0.7.2.

First and foremost, Bitbucket/Beanstalk/Unfuddle fixes. We've heard reports from users that posting changes against their Git repositories hosted on these services that just resulted in failure, so we've gone ahead and fixed that all up.

We've also fixed up some API caching brokenness when running against Review Board 2.0.13 and older. If you've ever tried to land a change clearly marked Ship It!, with an error saying it's not marked Ship It!, then you were hit by this bug.

(Oh, we had to disable some optimizations when running against 2.0.13 and older. You'll probably want to upgrade to the soon-to-be-released Review Board 2.0.14 as soon as you can.)

There are also two new RBTools commands for you to play with:

  • rbt login will log into a Review Board server and store the cookie. rbt post and other commands will still do that, but it's sometimes handy to have new users log in once in order to ensure they're all set up properly.
  • rbt logout will log you out of your API session on Review Board, and delete the cookie.

For the full list of changes, see our release notes.

Power Pack 1.2: Team Foundation Server, Flexible Licensing, and 2 Free Users Forever!

Power Pack 1.2 has been released with brand new support for Microsoft Team
Foundation Server and an all-new flexible licensing scheme.

As a bonus, we're also now offering 2 free licensed seats of Power Pack to
every Review Board server! See below for more information.

Microsoft Team Foundation Server

This release introduces support for reviewing code stored on
Microsoft Team Foundation Server
repositories. Team Foundation Server, or TFS, provides source code management,
project management, automated builds, and more, and is deeply integrated with
Microsoft Visual Studio.

With Power Pack, you can now configure all your TFS repositories quickly and
easily, without any of the custom scripts, patches, or workarounds that were
once needed. It's fully supported by the makers of Review Board.

Using RBTools 0.7.1 or higher,
developers can post or update changes against configured TFS repositories with
one command, without having to manually generate or convert diffs. Developers
can also view commits in the Review Board web UI and post any existing commits
for review with one click.

Note that currently, only TFVC repositories are supported. Git repositories
stored on TFS will be supported in a future update.

Flexible Licensing

In prior releases of Power Pack, a license had to be purchased for the entire
server. In larger companies, this made it difficult to justify Power Pack
licenses when needed only by select teams.

We've made our licensing model much more flexible. A license can now be
purchased containing a fixed number of seats, and those seats can be assigned
in a number of ways:

  • Manually assigned to specific users.
  • Manually assigned to all users in one or more review group.
  • Automatically assigned to users in one or more review groups whenever they join the group.
  • Automatically assigned to all users on a server when they join.

It's easier and more affordable than ever to get started with Power Pack.
Download a 30 day trial or
purchase a license for your team today!

Two Free Seats Forever!

Starting with Power Pack 1.2.0, all Review Board servers will be eligible to
receive two free, fully-licensed seats of Power Pack when downloading a
30 day trial license.

Once the 30 days are up, your license will convert to a full license for up to
2 people. This license will never expire, and supports all future releases of
Power Pack.

Simply purchase a license at any
time to bring the rest of your team or organization on board.

Review Board 2.0.13 is released

Today's release of Review Board 2.0.13 has a nice mix of bug fixes and features/improvements for Subversion users and administrators.

Let's get to the features first.

  • Subversion users with non-standard repository layouts will now find that they can now browse commits from any top-level directory in their repository in the New Review Request page. Previously, they were kind of stuck if they didn't have the standard trunk/branches scheme.

  • We've enhanced the administration UI to enable filtering/searching repositories (which is particularly useful if you have hundreds of repositories in your install). You can also search for any user and edit their profile information.

  • Also, we have a new authentication backend. If you're maintaining HTTP Digest password files for other services, and want those same accounts to work with Review Board, you're in luck! Simply enable the new HTTP Digest backend, point to your password file, and you're good to go.

If you're running RBTools 0.7.1 or higher, you'll be able to take advantage of enhanced caching support in our API, making everything just a bit faster!

We also have a number of bug fixes throughout the product. This covers crashes, visual issues, diff interaction/selection/parsing bugs, and more.

See the release notes for the full list of changes.

RBTools 0.7.1 is released

Today's release of RBTools 0.7.1 fixes up several issues found in this month's big 0.7 release, and helps to increase performance when posting changes for review. There are also compatibility fixes for Windows, and improvements to the new Windows installer.

Some of the highlights include:

  • Unicode compatibility fixes when running on Windows.
  • CVS/Subversion diffs are once again generated from the current directory and not the root of the checkout.
  • Several fixes for the Windows Installer.
  • Support for invoking RBTools in a Bash shell on Windows.
  • Fewer API requests are needed to post changes for review.
  • The API caching layer now depends on the upcoming Review Board 2.0.13.

For the full list of changes, see the release notes.

RBTools 0.7 is here!

RBTools 0.7 is packed with new tools and improvements for your workflow, making it faster to install, post changes to Review Board, and land your changes.

There's a lot here, so we'll go into the major new additions.

Easy installation for Windows and MacOS X

We've improved the installation experience. If you're on Windows or MacOS X, you can simply download the RBTools installer for your platform. In seconds, you'll be ready to use the latest RBTools.

Land reviewed changes with one command

The all-new rbt land is the fastest way to take a change (in a local branch or a review request), validate that it's been reviewed, and land it in your repository. It will format the commit message to include the review request's description and testing information, and can even handle pushing the change upstream and deleting the local branch in one go.

(This is currently only available for Git repositories. Support for other repositories will come soon.)

Exclude files from review

Sometimes you'll have modified files that you just don't want up for review. Auto-generated code, for instance. You can now exclude these when posting changes for review by using the new -X option to rbt post, or by setting EXCLUDE_PATTERNS in .reviewboardrc.

Make your own commands with aliases

Ever find yourself repeating a group of options? rbt post -g yes -u HEAD, for instance? In 0.7, you can create an alias -- a new RBTools command, basically -- for those options.

You can even go a step further and make an alias that runs non-RBTools commands. Want to always run unit tests before posting code? Make an alias. How about merging the latest upstream changes into your branch before posting? There's another alias!

See the documentation on aliases for more information.

Faster communication with Review Board

We've sped up RBTools by caching results from your Review Board server. This means lots of operations, such as posting changes, is faster than ever.

If you're using the RBTools Python API to write your own integrations, you'll benefit from this with no additional work on your end.

Supports Team Foundation Server

RBTools now supports posting changes against Microsoft Team Foundation Server. No more hacking together Subversion or Git wrappers for your repository.

This requires the upcoming release of Power Pack for Review Board. If you're interested in beta-testing Team Foundation Server support, let us know.

And lots more!

We haven't even talked about rbt stamp, support for API tokens, or all the bug fixes and other feature improvements.

Check out the release notes for the whole list of changes.

Announcing Review Board 2.0.12 with improved Markdown

Happy New Year, everyone!

Tonight's release of Review Board 2.0.12 brings about a large number of improvements to stability, performance, Markdown editing and rendering, e-mail control, repository compatibility, extension support, and more. It's one of our largest 2.0 releases yet.

Better Markdown support

We've completely overhauled our Markdown support. You can now disable Markdown when editing a field or a comment, which is useful when pasting or typing text that may not be Markdown-safe. All plain text fields will still be escaped for edit when you begin editing a field, so that you can easily add Markdown content.

We're smarter about how we escape content for Markdown now as well. You'll see fewer backslashes in your text.

If you prefer to edit all your fields in plain text by default, you can now do so by going into My Account -> Settings and unchecking "Always use Markdown for text fields." Any text fields saved as Markdown will still be loaded as Markdown, but now it'll be your choice.

Oh, and if you want to quickly spell check your text fields, just toggle Markdown off for a bit, and you'll get the browser's native spell checking back. You can then toggle Markdown back on when you're done.

The Markdown fields were a bit slow before, especially if the browser was bogged down. We've fixed this, and you should now have a much more comfortable typing experience.

Last, but not least, Markdown rendering is massively improved. We now preserve whitespace, blank lines, wrapping in lists, line breaks in lists, and the starting line numbers for lists. We have smarter language-based syntax highlighting (when using GitHub-style fenced code blocks), and we don't show unwanted backslashes in rendered text.

Better stability

We've fixed over 30 bugs, including issues with multi-threaded server setups, text selection in the diff viewer, CVS keyword processing, Unicode encoding issues with some copy/pasted text in text fields, auto-complete usability, and much more.

A broken extension is now less likely to break Review Board. Much of the custom code in extensions are sandboxed, preventing their errors from breaking anything else.

Support for Kiln and FogBugz

Are you a Kiln or FogBugz user? Good news! You can now review your code on Kiln with Review Board and link to your bugs on FogBugz.

Lots more

This post is already getting pretty long, so check out the release notes for the full list of changes in 2.0.12.

Power Pack 1.1.1 is released

This month's release of Power Pack 1.1.0 with Reports was very well received, though not immune to problems. As some users reported, we inadvertently broke compatibility with Review Board 1.7.x.

Today's release of Power Pack 1.1.1 fixes this compatibility issue.

We'll be announcing some brand new features and licensing improvements in the coming months for all new and existing Power Pack customers.

RBTools 0.6.3 released

Today's release of RBTools 0.6.3 fixes a handful of annoying little bugs across Git, Mercurial, Subversion, Perforce, and ClearCase. If you use any one of these (and there's a good chance you do), it's time to upgrade!

In past releases, failed post operations could leave behind incomplete review requests, which wasn't always obvious. RBTools will now print out the review request after a failure, making it easier to fix things up without creating a new review request.

We've also fixed a bug in the Python API for Review Board that resulted in errors when performing HTTP DELETE operations.

See the release notes for the complete list of fixes.

While this is a fairly small and bug-oriented release, we're happy to announce that RBTools 0.7 is coming soon, with several new features and native installers for Windows and MacOS X! If you're reading this in your browser, please subscribe to our mailing list for announcements!

Power Pack 1.1 is released

We've just released a new build of Power Pack, our premium set of features for Review Board. Power Pack includes support for GitHub Enterprise, PDF review, and more.

Power Pack 1.1 adds a major new feature: Reports.

Power Pack Reports

Teams of all sizes can benefit from analyzing and measuring the effectiveness of code review amongst their developers. Better insight leads to better, more cost-effective processes and policies. To help with this, we're adding five different ways of looking at your code review process:

  • Time to First Feedback

    This helpful graph shows how long, on average, it takes for new changes to be reviewed. See where the bottlenecks are in your team.

  • Time to Close

    Some code reviews hang on for far too long, delaying releases. See how often this is happening, and where.

  • Review Request Statistics

    A quick at-a-glance table showing statistics on how frequently team members post review requests, how many issues they typically have filed against them, and how many of those are dropped instead of fixed.

  • Code Review Statistics

    More detailed metrics on the actual code reviews performed within the team. See who on your team are more actively reviewing code, how many issues they tend to find, and how frequently they mark Ship It! You'll have a better sense of who is really engaged in the code review process.

  • Code Review Relationships

    This eye-catching diagram shows who's more actively reviewing who's code. It provides a great way of quickly seeing which parts of your team are working closely together, and who's not pulling their weight.

See the release notes for more information.

To install or upgrade Power Pack, simply run:

sudo easy_install -U ReviewBoardPowerPack

To get a trial or purchase a license, see the Power Pack page.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 pages