On 10/11/2015 8:01 AM, Ali Nazemian wrote: > I did check the jira issue that you mentioned but it seems its target is > Solr 6! Am I correct? The patch failed for Solr 5.3 due to class not found. > For Solr 5.x should I try to implement something similar myself?
Virtually all changes that are made to Solr are done first in trunk (currently trunk is slated to be the 6.0 release) and then are backported to the stable branch (currently branch_5x). If a change is particularly controversial, difficult to directly and reliably test, very large, or breaks backward compatibility in a major way, then it may not get backported to the stable branch. The feature will remain unreleased until a large amount of work is completed to make a new major version ready for release. Sometimes a new feature will be committed to trunk, worked on for several weeks or months to make sure it's ready, and *then* get moved to the stable branch for release. I admit to not really understanding what SOLR-7584 is about, but if the code (when it's fully done) is solid and includes some tests to make sure it works, it doesn't look like something that needs to wait for 6.0. The patch is somewhat large, at 50K, but it looks like the bulk of it is new code, not large-scale changes to existing code. Thanks, Shawn
