: > Is there any thinking about when that might drop (beyond the quite : > understandable "when it's done")? Or, perhaps more reasonably, when it : > might freeze?
FWIW: I have no idea ... it's all a question of when someone "takes charge" on the release process -- quite frankly, so much is in flux right now (because of the java+solr code tree merges, *and* the decision to create parallel dev branches so the trunk could be more agressive about API changes, *and* the decision to refactor modules) that i suspect a lot of things kind of need to "shake out" before anyone is going to feel comfortable doing a new release : I'm also interested in the recommend "testing" branch (to borrow a : Debian term) to use. I'm planning a deployment in 2 months or so and : have been experiencing too many problems with the older version of : Tika to use the 1.4 version. FWIW: If the only problem you are having with 1.4 is that you want o upgrade Tika, patching 1.4 to make hte neccessary changes to use a new version of Tika is probably going to be far less invasive/risky then using the 3x branch (but that is only my opinion, and i'm not even that well informed about what it takes to upgrade the Tika dependency) -Hoss
