That could be months of haggling and I don't think we should hold up all the other nice features, improvements, and bug fixes for too much longer as we don't want to slow down adoption of 5.x
Without any judgement of what was done in SOLR-7214 and given that SOLR-6348 has precedent, why not mark the new JSON API as experimental, giving us freedom to unify the approaches over the next several releases? On Wed, Mar 25, 2015 at 10:30 AM, Steve Molloy <[email protected]> wrote: > I think something should be done about SOLR-7296 before releasing. IMHO, > having 2 implementations and completely unrelated APIs for facetting is > asking for problems down the road. So before exposing this publicly, we > should either align implementation or at least the dev group needs to > consciously make the decision to move ahead with this, understanding the > drawbacks. > > Steve > ------------------------------ > *From:* Timothy Potter [[email protected]] > *Sent:* March 25, 2015 1:17 PM > *To:* lucene dev > *Subject:* Creating 5.1 branch soon ... > > Hi, > > I'd like to create the 5.1 branch soon'ish, thinking maybe late tomorrow > or early Friday. > > If I understand correctly, that implies that new features should not be > added after that point without some agreement among the committers about > whether it should be included? > > Let me know if this is too soon and when a more ideal date/time would be. > > Sincerely, > > Your friendly 5.1 release manager (aka thelabdude) > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected]
