I appreciate the encouragement Houston, I was starting to flag a bit on this…
One thing I noticed is that some of our tools, like the ZK related ones, use
the shell code to do arg parsing, and then we pass them into Java. Those will
still work with old and new parameters, but until we move the
I definitly struggle with this. I wonder if we need a brand new approach that
isn’t encumbered by historical patterns to get us moving forward on this?
What if we changed it to something that focused on the different constituencies
of Solr.
* Changes Impacting Search Developers
* Change
When I think of CHANGES.txt, I think of communicating to users. We
write something succinct for the benefit of users to understand how
this change will impact them.
I don't think of CHANGES.txt as a log of all changes. I think
increasing the scope to such wastes the time of users (and *we* are
a
