Notes on the commit I just did -- Holy Macinaw, there's been a lot of changes checked in since our last release (2.2.0). Enough to make me a little nervous about 2.3 - Ideally we would release in a much more incremental fashion to reduce risk. In fact I wonder if we ought to talk about modularising some of the later changes so that use of the new code is optional, or perhaps planning a series of point-releases.
In any case, on the 2.2 branch I applied the fix for RIVER-149 plus some documentation updates. The changes after that seem to be related to the concurrency items that are currently being worked on in the trunk. I'm currently running the test suite locally. Depending on the results we'll see about rolling release 2.2.1. Cheers, Greg.
