The release vote has now been called off due to PYLUCENE-50.
Andi..
On Mon, 17 Jun 2019, Andi Vajda wrote:
On Mon, 17 Jun 2019, David Allouche wrote:
On 17 Jun 2019, at 20:42, Andi Vajda <va...@apache.org> wrote:
On Mon, 17 Jun 2019, David Allouche wrote:
Thank you, that was very informative.
+0 for this release, I builds and pass my test suite.
But I was unable to make a complete integration test because I do not
have a proper index format migration infrastructure and my index is made
of incompletely-upgraded lucene6 and lucene7 segments.
So far, you're the only one who has cast a vote.
No one else, no PMC member, none of the longtime users, no one.
Marc Jeurissen did +1.
Oops, I missed this message. It is in my inbox, however.
My bad.
Milo just voted +0.
So, after the vote being open for a week, we have:
- one +1 vote (Marc's)
- two +0 votes (yours and Milo's)
- one +1 PMC vote (mine)
For a release to happen, we need two more PMC votes.
Andi..
Message-Id:
<5cff4939.1c69fb81.2d212.8174smtpin_added_miss...@mx.google.com>
And since you posted your message, Milo H Fields III did +0.
So there _is_ interest.
I do have a long-term need for PyLucene, but I really just need one release
per major version to have an index upgrade path. But it seems like Lucene
Core make major releases quite frequently nowadays.
