Hmm not sure why the original mail CC'd pylucene-...@ovaltofu.org :)

+1 to release.

I ran my usual smoke test, on Ubuntu Linux 16.04.6 box, using Python 3.5.2
and Java 11.0.2: index and search first 100K wikipedia documents.

I had to modify my small Python pylucene smoke testing tool to change
IndexWriter.numDocs() to IndexWriter.getDocStats().numDocs :)  And then it
ran correctly.

Mike McCandless

http://blog.mikemccandless.com


On Tue, Apr 28, 2020 at 3:53 PM Michael McCandless <
luc...@mikemccandless.com> wrote:

> I will review and vote soon!
>
> Sorry for the delay!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Apr 25, 2020 at 4:05 PM Andi Vajda <va...@apache.org> wrote:
>
>>
>>   Hi Lucene PMC members,
>>
>> Please, consider voting for the current PyLucene 8.3.0 release candidate.
>> The vote has been open since Nov 3rd, 2019 (!) and we still need two more
>> PMC votes to release.
>>
>> Thanks !
>>
>> Andi..
>>
>> ---------- Forwarded message ----------
>> Date: Sun, 3 Nov 2019 17:52:54 -0800 (PST)
>> From: Andi Vajda <va...@apache.org>
>> Reply-To: gene...@lucene.apache.org, Andi Vajda <va...@apache.org>
>> To: pylucene-dev@lucene.apache.org
>> Cc: gene...@lucene.apache.org
>> Subject: [VOTE] Release PyLucene 8.3.0
>>
>>
>> The PyLucene 8.3.0 (rc1) release tracking the recent release of
>> Apache Lucene 8.3.0 is ready.
>>
>> A release candidate is available from:
>>    https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.3.0-rc1/
>>
>> PyLucene 8.3.0 is built with JCC 3.7, included in these release artifacts.
>>
>> JCC 3.7 supports Python 3.3 up to Python 3.8 (in addition to Python 2.3+).
>> PyLucene may be built with Python 2 or Python 3.
>>
>> Please vote to release these artifacts as PyLucene 8.3.0.
>> Anyone interested in this release can and should vote !
>>
>> Thanks !
>>
>> Andi..
>>
>> ps: the KEYS file for PyLucene release signing is at:
>> https://dist.apache.org/repos/dist/release/lucene/pylucene/KEYS
>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/KEYS
>>
>> pps: here is my +1
>>
>

Reply via email to