-1 on release early often.
Let us say you average 6-8 releases a month, this means there will be that many
versions used by users. Which means the amount of testing done on a release
(by real users, in real environment) will be spread thin thus a release will
not get the same amount of
My bad, I meant to say a “6-8 releases a year” .. grrr!!
So let me try this again. I don't like the current plan of release early
often because:
So let me try this again. I don't like the current plan of release early
often because:
1) It will spread testing thin of any release because
Hi,
Looking at http://wiki.apache.org/lucene-java/ReleaseNote32, the item:
* A new IndexUpgrader tool fully converts an old index to the
current format.
Where can I learn more about this? Is this for upgrading the Lucene index from
Lucene 2.1 to 3.2 due to the analyze change?
My
So, in my case, upgrading from Solr 1.2 to 3.2, I must re-index. OK, I got
that, thanks.
Btw, where can I learn more about the new IndexUpgrader tool? Is there a
doc/wiki for it?
-JM
-Original Message-
From: Uwe Schindler u...@thetaphi.de
To: dev@lucene.apache.org
Sent: Fri, Jun
I'm confused. So, if I'm upgrading from Solr 1.2 to 3.2 and I don't change my
analyzer type=index and analyzer type=query sections, I don't have to
re-index my data?! I was told otherwise (i'm trying to find that post) because
the analyzers have changed. In case it matters, i'm using
Too many releases maybe a bad idea, not only will there be too many questions
to users such as what version are you using, have you tried version X, the
latest, etc. but you may lose your trust with some of the more serious
organizations who see stability ahead of frequent releases.
-JM
