On Aug 6, 2008, at 1:16 AM, Shalin Shekhar Mangar wrote:
On Wed, Aug 6, 2008 at 1:16 AM, Grant Ingersoll
<[EMAIL PROTECTED]> wrote:
Well, we've been beating around the bush on 1.3 for a good amount
of time
now. How about we set a date and actually vote on it and thus
make it
pseudo-binding?
+101 :)
SOLR-630: Spellchecker should not be case-sensitive and should be
stopwords
aware. No patch available or unit tests. Seems like it could be
handled
through analysis, but not sure.
I think the same. Will find some time look into it.
SOLR-506: Enabling HTTP Cache Headers should be configurable.
Sounds
ready to commit, right Shalin?
Correct.
SOLR-614: Allow components to read any kind of XML. Has a couple
of -1 on
it that have been changed to -0
I'm very much +1 for it. Will review and commit soon.
Um, I don't know if committing is what is supposed to be done here.
There seems to be a general lack of enthusiasm for it, with several
-1's that were changed to -0, which is not exactly encouraging. My
gut says it should wait.
0. Accept no more issues outside of this list, other than blockers
for 1.3.
I'd like to add support for publishing artifacts to maven since it
is very
useful for a lot of people. We have 2 issues related to this.
SOLR-19 and
SOLR-586. However, it should not stop us from releasing 1.3
+1. I'd just copy what Lucene does.
1. Set August 12 as code freeze date. 1 week from today. After
which,
only doc changes and blockers are allowed. So, if the above isn't
fixed by
then, it's out unless someone wants to make it a blocker.
+1 for August 12
2. Code Freeze in effect for 5 days for testing of release
candidates.
Thus, the 1.3 release, assuming all goes well will be on the 17th
or 18th
(since the 17th is a Sunday.) Thus SOLR-489 in theory need not be
complete
by the 12th, but the 18th instead, although we might as well get it
done.
