Things are for all intents and purposes, at the point where my train stops. The next sensible train is likely, really the one you wanted to board. And that is looking at what short term value and experiments and results can likely be harnessed and converted from the issues I create in a fork into Solr proper issues.
That is going to to be a tough part for me. And won’t include what some would like. There is a longer term thing Ive found around resource usage and test performance and stability and the myriad of things our tests won’t catch. That’s high value that is all entangled and comprehensive, and I won’t be killing myself on a tougher path to that in Solr proper after killing myself on a path to that. But there remains a lot of stuff to look at and take value from. That’s not something I’m going to be great at driving - I’ll drive stuff that comes from carear driven needs. So as I drop the notes and make it easier to test drive and experiment with the branch, this is where you can add value. Helping to drive what brings value based on your own experiences and external pressure, and helping to extract that value. Where I can add value is in helping on that effort, but independently, anything i do will be mostly driven by needs outside my own in the short term. Mark -- - Mark http://about.me/markrmiller
