Is there any discussion yet of shipping this feature in 1.x as opposed to 2.0?  As Jeff wisely points out, the multitude of branches does become overwhelming for keeping bug fixes in sync across all.

Is it simple enough to keep it as a patch, for now, which you could easily apply to 1.6.x branch if and when it were created?

On Thu, Jun 6, 2013 at 10:36 AM, Graham Leggett <> wrote:
On 06 Jun 2013, at 5:24 PM, Jeff Trawick <> wrote:

It makes sense to have it once we have changes that someone wants to release in 1.x but which can't be released in 1.5.x.  (I guess you already have such changes in mind so go for it ;) )

Indeed I have :)

As we've had some trouble in the past keeping such next-1.x branches up to date (mostly minor stuff like doxygen improvements that skipped 1.latest), I think it is best to defer until actual use. 

I am ready to backport and, but have nowhere to backport it to.