I suppose it's debatable wether public knowledge of a version being released or not is itself sufficient to serve this purpose. I certainly am keenly aware of the latest version as I think we all are here? Personally I'd prefer the simplicity of one less state but I don't care that much either.
On Fri, Apr 7, 2017 at 1:08 PM Chris Hostetter <[email protected]> wrote: > > : For me I use "closed" to figure out if an issue was just committed or if > : there is already a release out there. So to me it is natural to close > > And to continue that line of thinking: the reason this should be important > is so that we don't inadvertantly "tack on" any work/tweaks to issues that > have already been released. > > If SOLR-XXXX is a bug fix that was committed to the 6.Y.Z, but after 6.Y.Z > is released people discuss/debate the merits of tweaking the fix, the fact > that 6.Y.Z is already out -- and SOLR-XXXX is "Closed" -- is the reminder > that this change should be tracked in a new, distinct, jira ... if for no > other reason so that the "new work" has it's own Jira to be listed under > in CHANGES, but also so that if/when we talk about a bug that was > "fixed by SOLR-XXXX" people looking at that jira can all be on the same > page about what that means, and what releases include that fix. > > > > -Hoss > http://www.lucidworks.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
