On Thursday 06 June 2013, Graham Leggett wrote:
On 06 Jun 2013, at 5:24 PM, Jeff Trawick traw...@gmail.com 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
Hi all,
I notice that we don't have an apr-util v1.6 branch at
https://svn.apache.org/repos/asf/apr/apr-util/branches/.
Obviously there is no trunk branch, as trunk merged with apr, however ideally
we still need a branch for further development in the v1.x stream.
Should I create an apr-util
On 06.06.2013 17:00, Graham Leggett wrote:
Hi all,
I notice that we don't have an apr-util v1.6 branch at
https://svn.apache.org/repos/asf/apr/apr-util/branches/.
Obviously there is no trunk branch, as trunk merged with apr, however ideally
we still need a branch for further development
On 06 Jun 2013, at 5:24 PM, Jeff Trawick traw...@gmail.com 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
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
