[
https://issues.apache.org/jira/browse/SOLR-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042465#comment-13042465
]
Robert Muir commented on SOLR-2567:
-----------------------------------
bq. Additionally, I dont think its a problem to respin because of that.
You are right, its no problem at all to respin, I don't mind doing this at all.
The only problem is that committers must spend their time to re-review the
release candidate, but I suppose if they watch the commits list they can be
more confident in their checking and not have to waste a lot of time, since its
only this issue and maybe two other small things that were found.
In fact, Mike committed a "HuperDuper" automated-checker to do some of the
grunt work of checking a release to luceneutil today:
http://code.google.com/a/apache-extras.org/p/luceneutil/source/detail?r=5bf3a0ea4922bbeb38a0a16c503b42e07c028eab
So maybe its a good opportunity to use this utility to aid in easier review of
release candidates.
> Solr should default to TieredMergePolicy
> ----------------------------------------
>
> Key: SOLR-2567
> URL: https://issues.apache.org/jira/browse/SOLR-2567
> Project: Solr
> Issue Type: Bug
> Components: update
> Reporter: Robert Muir
> Fix For: 3.3, 4.0
>
> Attachments: SOLR-2567.patch, SOLR-2567.patch
>
>
> even if we set a luceneMatchVersion to >= 3.2 (SOLR-2557),
> Solr still defaults to LogByte
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
