: > which should not be an indication that the code in question will not : > function correctly. Also, there isn't a peep of warning in CHANGES.txt
: I was waiting for SOLR-360 to add the CHANGES.txt for multi-core related : things. You are right, the deprecated API deprecations and alternatives need : to go in ASAP. we should try to make notes in CHANGES.txt in the same commit as the changes themselves ... that way people doing their own builds can get an accurate idea of what's changed by diffing the file ... rough descriptions of changes that we plan on cleaning up later are better then no description. : I think there is a way to maintain backward compatibility, but it is not : totally straightforward (so i can't do it right now) being offline and out of hte loop for a few days has left me a little confused as to what exactly the imcompatibility is ... could someone open an issue summarizing the problem and mark it fix for 1.3 .. that way we'll have a reminder to either get a fix in, or document the hell out of it as a known incompatibility (which would suggest 1.3 be renamed 2.0, but i'm not sure how neccessary that is without a better understanding of how bad the incompatibility is) -Hoss
