We've just put out an all-new release of RBTools. Version 0.7.7 features compatibility fixes for various types of repositories, better support for TFS, and some new features to help with common usage and automation.
You can see the release notes for the full list of changes. We'll go over the highlights here.
Compatibility/bug fixes
In this release, we've aimed to fix a handful of compatibility problems that have been reported to us. Thanks to all the contributors who sent patches!
- RBTools is once again compatible with Mercurial 2.x. This regressed in 0.7.6.
- Some error displays are fixed when using the version of Python shipped with macOS 10.11.
- Perforce gained the ability to post against null client roots, and fixed posting ranges of submitted changelists.
- Repository lookups utilizing mirror paths or Subversion UUIDs now work once again. These regressed in 0.7.6.
- rbt post for Git now supports
--exclude-patternswhen usinggit-svnorgit-p4. - rbt land no longer crashes if it can't determine the approval state on a review request.
Improved Team Foundation Server support
The old TFS support was a bit slow, due to the way we had to interact with the Team Foundation Server command line tools. It also presented compatibility problems, as different versions of Visual Studio shipped different, incompatible versions of these tools.
We've now introduced new support that doesn't depend on their tools and is optimized for our use cases. This means better compatibility everywhere, faster posting, and new features.
To start with, we're adding the ability to post shelved changesets! You can do this by simply running:
rbt post <shelveset-name>
To begin using RBTools 0.7.7 with TFS, you will need to install our new TFS adapter by typing:
rbt install tfs
New features
We've added the ability to specify a destination tracking branch for rbt land. To choose something other than the default (say, origin/master on Git), you can now specify:
rbt land --tracking-branch <branch-name>
Want to set some some data for custom extension-provided fields on your review request when posting a new change? You're in luck! We've added a --field NAME=VALUE option to rbt post that does exactly this:
rbt post --field my_custom_field="Some value"
You'll need to use the name of the field that was registered by the extension. If this extension was written in-house, ask your administrator to give you the field IDs.
If you find yourself needing to pass --svn-prompt-password all the time for your Subversion setup, you can set SVN_PROMPT_PASSWORD in your project's or user's .reviewboardrc instead. Just set this and you'll never have to type it again:
SVN_PROMPT_PASSWORD = True
What's coming next
We're working toward a RBTools 1.0 release, which will feature enhanced support for Mercurial, new automation commands for use in the upcoming Review Board 3.0, easier setup and installation, and better display of progress when posting changes.
We're also hard at work on a rewrite of our documentation, with the aim of providing more practical, detailed setup and usage guides for RBTools. These will begin to land over the next month.
If you have any bug reports or feature requests for either RBTools or the documentation, we'd love to hear them! You can file a bug or reach out to us on our reviewboard-dev discussion list.