We have another release for you today. Review Board 2.0.21 is out, adding support for Assembla repositories (already available in 2.5), e-mail improvements, extension enhancements, and several bug fixes.
Many of these enhancements and fixes were backported from 2.5. For example, e-mails will now show "Fix it, then Ship It!" if a reviewer submits a "Ship It!" review with issues opened.
There are several bug fixes you'll also enjoy:
Viewing an interdiff containing a draft diff and then updating that draft diff no longer shows the old interdiff.
Updating a review request when it and another review request depend on each other no longer results in errors.
Commits against a local GitLab server no longer fail to post.
Default reviewers are now applied when posting an existing commit for review on the New Review Request page.
Database upgrades from older versions of Review Board should now work consistently.
There are also numerous visual improvements and other small fixes here and there. Check out the release notes for more details.
Please note that in order to upgrade to 2.0.21, you must do:
$ pip install ReviewBoard==2.0.21
$ easy_install ReviewBoard==2.0.21
If you don't specify a version, you'll get the latest 2.5.2 release instead.
Don't forget to upgrade to our Django 1.6.x security updates build. This can't be done automatically just yet. See our announcement for more information.
Review Board 2.5.2 has been released for your downloading pleasure, featuring a couple feature changes and several bug fixes for e-mail, image/PDF review, GitLab, webhooks, and more.
First off, we've made it easier for administrators to figure out how to set up GitHub Enterprise and Microsoft Team Foundation Server repositories. These require an installation of Power Pack, but that wasn't immediately obvious to those unfamiliar with that option. Now, both GitHub Enterprise and TFS are always listed when configuring a repository, and if Power Pack is not installed, it will point administrators in the right direction.
We've also fixed:
Issues upgrading from certain older releases.
Missing "Ship It!" and "Fix it, then Ship It!" indicators in review e-mails.
Payload errors for comments on review replies in webhooks.
Problems posting existing commits on self-hosted GitLab repositories.
Interaction and performance issues with moving draft comment regions on images and PDFs.
Compatibility issues with current releases of Power Pack when it comes to clicking on comment regions on PDFs.
Inability to double-click to select text in a diff.
Bad output and annoying (but harmless) crashes when running the condensediffs management command, used to reduce database size.
Today, Django released new security patches for 1.7.x and 1.8.x, and 1.9. These fix a possible settings leak in the date template filter, enabling a user to steal settings like a database password if they're able to construct their own date format string.
We've put out a corresponding 22.214.171.124 release, which backports this fix to the version of Django used by Review Board 1.7.x through 2.5.x. While this vulnerability does not affect Review Board, we nevertheless suggest that you upgrade.
Unfortunately, due to restrictions in the design of pip, we will not be able to automatically upgrade to these versions of Django in Review Board. We are working on a solution for this. However, for now, it will be up to you to handle this.
Please note that Django 1.6.x is the last version to support Python 2.6.x, which has also end-of-lifed. We will be dropping support for Python 2.6 in Review Board 2.6, so we recommend moving to Python 2.7 at your earliest convenience.
Last week's release of Review Board 2.5.1 was a huge hit, and we've had a lot of people quickly upgrading to try out all our new features. If you haven't had a chance to see the release yet, check out our video introduction.
However, it wasn't a perfect release, and many of our Python 2.6 users noted that summaries were no longer showing in the dashboard, due to a compatibility issue introduced in 2.5. We've addressed this and several other issues in today's release of 2.5.1.
Along with the bug fixes, we've made improvements to diff display and for posting new commits for review.
Thanks to everyone for testing the release, sharing it with others, and providing great feedback!
Updated November 3, 2015 23:40 PST: We've released 126.96.36.199, which temporarily reverts the new feature from 2.5.1 for including branch information in posted commits, due to some breakages that resulted.
We are proud to announce the immediate availability of Review Board 2.5. You’ve helped make Review Board a hugely popular tool, with hundreds of thousands of users worldwide, and we think you’re going to love 2.5!
We really pushed ourselves to improve the tool’s extensibility, to give you even more ways to make Review Board a reliable, hassle-free part of your workflow. We’ve incorporated feedback from our users around things like mobile support, improved collaboration capabilities and usability improvements that make developers’ jobs easier.
Here are some of the highlights:
A cleaner, more polished look and feel
A cleaner Review Board is a friendlier Review Board. We've removed a lot of the noise and cruft, and helped bring your attention to what matters most.
Work on the go with new mobile support
On a train? Out to lunch? No problem! Review Board 2.5 is mobile-friendly, so developers can contribute to reviews while away from their desk.
Review faster with Expandable Diff Fragments
Instantly see more context for a comment. One click expands the diff right in the review.
Stay focused by muting and archiving review requests
For all the Inbox Zero types, you can now archive old review requests and mute any that don’t require your attention.
Auto-version and diff your file attachments
Just upload a new version of an attachment and Review Board will track its version, letting everyone see all the changes made. Images and text-based attachments can even be diffed!
See more at a glance with Live HD Thumbnails
Hover over file attachment thumbnails and watch as more of it scrolls into view, giving you a better picture of what's in the file.
Integrations to Power Your Workflow
Share your credentials securely with API Tokens
Third-party tools/services and custom scripts can now securely log in as a Review Board user. No need to give out passwords, and the access can be tightly restricted. This paves the way for future integrations with things like third-party automated code review services.
Hook into other services with Webhooks
Review Board 2.5 can notify other services, such as collaboration and CI tools, in a format they understand when posting or updating review requests and reviews.
Deeper integration with bug trackers
Connecting your JIRA, Bugzilla, or GitHub bug trackers to Review Board lets you see more detail about the bugs on your review requests.
You can see some of this in action by watching the video below:
"As both a heavy Review Board user and a contributor, I’m very excited about release 2.5," said Stephen Gallagher of the Fedora Project. "The Beanbag team and entire Review Board upstream open source project exemplify all the ideals of the open source movement: agility, collaboration and community. The interface improvements in 2.5 really make Review Board feel like a tool for today’s developer. And as I’m increasingly away from my desk, mobile support to keep up with reviews on the go is critical."
Griffin Myers, a developer with a leading maker of high performance signal processing applications, added "Review Board is an indispensable part of our development process. It helps increase collaboration within our team, improves code quality, and provides a pathway for new team members to become assimilated with a large existing code base. The Beanbag team has cultivated an active user community and is incredibly responsive to, and receptive of, user feedback. I’m most excited about 2.5’s restyled UI, improved mobile support, and expandable diff fragments. We also love the enhancements to Markdown rendering, e-mail and dashboard management, all of which have their roots in user requests."
This is largely a bug fix release, focusing in part on improved compatibility with Windows, Git, Subversion, Mercurial, Perforce, and Team Foundation Server.
On Windows, RBTools will now first look in %HOME% to find any custom .reviewboardrc files, instead of only looking in the Application Data directory, which will be quite helpful with many system configurations. There are also fixes for using Mercurial on Windows.
Non-Git user? You've probably seen that annoying but harmless command not found: git error when posting a change. That's gone now!
For Perforce users, posting submitted changes or files outside of the client view now work. This had regressed in an earlier release, but you should be in good shape now.
Subversion has seen some more Unicode fixes, plus fixes for rbt post --svn-show-copies-as-adds.
Along with all this, we've added a new feature for setting a custom search path for .reviewboardrc. You can set your $RBTOOLS_CONFIG_PATH to a list of paths to search, allowing you to make your version in $HOME take precedence over what's in your repository, and allowing you to work with centralized collections of aliases in your organization.
Power Pack 1.3.4 builds on top of last release's 1.3.3, fixing a couple of annoying bugs.
First, some of you have found that Reports broke in 1.3.3. We've tracked the issue down and fixed it. Reports should work just fine now.
Beta users of Review Board 2.5 have noted that one of our new features didn't work so well with Power Pack. Review Board 2.5 allows any draft comments on an image or document to be moved and resized, but this didn't play nicely on PDFs. That's been taken care of, so once you upgrade to 2.5, you'll be able to drag those comments all over the place.
It's a small release, but we have some big ones coming up, as we prepare some major improvements to Reports, and introduce some new features to help manage user accounts.
Power Pack 1.3.3 is now available for download, featuring new bug fixes and an improved setup and trial experience.
Power Pack extends Review Board, offering PDF document review, report generation, scalability, and compatibility with Microsoft Team Foundation Server and GitHub Enterprise.
We've fixed case sensitivity issues when comparing paths with TFS, fixing issues when posting diffs. There are also compatibility fixes for systems using Python 2.6.
Along with this, we've made it easier to get started with Power Pack. When you first install it and enable the extension, you'll see a new banner guiding you through installing a trial license, and then guiding you through adding users to the license. Once your trial runs out, it'll let you and your users know, so that there's no confusion as to why features stopped working.