On 11/21/2014 1:14 PM, Alexandre Rafalovitch wrote: > I am writing something that - will - depend on Solr 5. As I usually > work with released versions, I am not entirely sure of the correct > workflow. > > I can check out branch_5x and do my research against that. I assume > that's the correct source for what will land in version 5. > > But if I find an issue, do I then report it against 5? Or do I need to > retest that against trunk and report against trunk? I don't know how > in-sync these two are at this point. > > I've checked https://wiki.apache.org/solr/HackingSolr but it is not > specific enough (and is actually out of date regarding version 5).
Any testing we do for branch_5x probably isn't enough, so please do test with it. That is the branch where development will happen for all 5.x releases. If you do find a problem and *can* try again with trunk, please do, but don't make that a prerequisite for filing an issue or creating a patch. A patch against trunk is preferred, but any patch is better than none. We'd like to know which branch the patch applies to, and if there are any problems we may need to know the SVN revision number, so it's better to include that info up front if you have it. If you are using one of the git mirrors, the SVN revision number may not be available. The git commit hash may be useful instead. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
