Form me it does not matter, but when I open new issues, I do it against the project where the “bug” is visible. If there is also code committed to Solr, but the main task is Lucene this is fine.
If we have a new functionality that affects both projects, you can create a secondary issue in the other project and link them. Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Robert Muir [mailto:[email protected]] Sent: Wednesday, August 18, 2010 10:03 PM To: [email protected]; [email protected] Cc: [email protected] Subject: Re: Combined Lucene/Solr Issues On Wed, Aug 18, 2010 at 3:55 PM, Simon Willnauer <[email protected]> wrote: I would appreciate creating two issues and use one only for reference and link it by the one which contains patches and discussion if the changes are large. Using SOLR- vs. LUCENE- I'd decide on a case by case basis depending which "project" / "codebase" might undergo the most significant changes. Generally, referencing the issues in CHANGES.TXT sounds like a good idea. I don't think this is realistic. often a patch needs to change lucene and solr code in one commit. Personally, i don't waste any time thinking about whether the issue is SOLR or LUCENE, and I think two JIRAs is actually confusing. -- Robert Muir [email protected]
