Hi guys, new subscriber here, so as a bit of an intro, I'm a long time user of Lucene/Solr from Lucene 1.x. I've plugged everything pluggable and am quite familiar with the core Lucene and solr code. Looks like I should have sent this to dev instead of solr-user:
I'd like to get your tips on how to run a Solr fork at my company. I know Yonik has a "heliosearch" fork, and I'm sure many others have a fork. There have been times where I want to add features to an existing core plugin, and subclassing isn't possible so I end up copying the source code into my repo, then using some crazy reflection to get it to work. Sometimes there's a little bug in something and I have to do the same thing. Sometimes there's something I want to do deeper in core Solr code that isn't pluggable and I end up doing an interesting workaround. Sometimes I want to apply a patch from JIRA. I also think forking solr will make it easier for me to contribute patches back. So here are my questions: *) how do I properly fork it outside of github to my own company's git system? *) how do I pull new changes? I think I would expect to sync new changes when there is a new public release. What branches do I need to work with/on? *) how do I test my changes? What part of the test suites do I run for what changes? *) how do I build a new version when I'm ready to go to prod? This is slightly more unclear to me now that it isn't just a war. Thanks, Ryan
