I guess it depends on if your planning a 1.4 release with lucene 4. If yes then merge and work towards making everything functional. If not then leave the 1.3.x in master for bug fixing or whatnot and merge this branch into the new api one. On Oct 20, 2012 11:03 AM, "Aaron McCurry" <[email protected]> wrote:
> I think that we can merge the lucene-4.0.0 branch back into the > master, since tests and code are compiling. I haven't done any > functional testing yet, but if much of the RPC and internals are going > to change I think that it may be a waste of time to test and fix > everything that we are about to change. What do others think? > > Aaron >
