I suspected as much, and simply wanted to confirm/prod. Keeping "new" features from here-on-out on a branch is totally fine with me. Alternatively, placing them under an #ifdef like we did with the obliterate support works well, too. (and yes, I realize Java can't do that very easily...)
Cheers, -g On Wed, Sep 8, 2010 at 13:58, Hyrum K. Wright <hyrum_wri...@mail.utexas.edu> wrote: > On Tue, Sep 7, 2010 at 5:56 PM, Greg Stein <gst...@gmail.com> wrote: >> I don't see a README.branch or whatever it should be named... > > Thanks for the reminder, I've added one in r995168. > >> What is this branch for, and why is it not on trunk? > > The purpose is to expose some of the RA-layer APIs in JavaHL. The > reason for a branch is that > a) I'm unsure how complete this work will be, or its timeline for > completion, meaning that > b) I'm not comfortable doing it on trunk where it might be released > > Rather than add more stuff to the JavaHL bindings, and conflate what > is already there with this new work, I'd rather have it stay on the > branch until it feels "ready" or we branch 1.7. > > If there are arguments to the contrary, I'm happy to move it to trunk, > however. > > -Hyrum > >> On Tue, Sep 7, 2010 at 18:00, <hwri...@apache.org> wrote: >>> Author: hwright >>> Date: Tue Sep 7 22:00:57 2010 >>> New Revision: 993544 >>> >>> URL: http://svn.apache.org/viewvc?rev=993544&view=rev >>> Log: >>> On the javahl-ra branch: >>>... >> >
