(Comments on SOLR-2191 between Mark & I were starting to get off-topic with respect to the issue so I am continuing the conversation here)
A lot of JIRA issues seem to fall off the radar, IMO. I'm talking about issues that have patches and are basically ready to go. There are multiple ways to address this but at the moment I am going to just bring up one. Looking at the versions in JIRA one can assign an issue to https://issues.apache.org/jira/browse/SOLR#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel I see the version named "Next", with this description: "Placeholder for commiters to track issues that are not ready to commit, but seem close enough to being ready to warrant focus before the next feature release". This version and what it implies is a common pattern in use of JIRA that I too use for projects I manage for my employer. It appears that for the 3.1 release, nobody looked through the issues assigned to "Next", and consequently, some issues like SOLR-2191 were forgotten despite being ready to go. Looking through the wiki I see information on how to do a release http://wiki.apache.org/solr/HowToRelease and release suggestions but no information on what to do in advance of a release. I also don't see any administrative tasks on managing the "Next" version in JIRA. So I think either the "Next" version should be used effectively, or if that isn't going to happen then delete this version. On a related note, I don't know what to make of the "1.5" version, nor what to make of issues marked as Closed for "Next". Some house cleaning is in order. Thoughts? ~ David Smiley ----- Author: https://www.packtpub.com/solr-1-4-enterprise-search-server/book-- View this message in context: http://lucene.472066.n3.nabble.com/jira-Created-SOLR-2191-Change-SolrException-cstrs-that-take-Throwable-to-default-to-alreadyLogged-fae-tp1763003p2878021.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
