You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pylucene-dev@lucene.apache.org by Andi Vajda <va...@apache.org> on 2019/03/05 20:08:24 UTC
[VOTE] Release PyLucene 7.7.1
The PyLucene 7.7.1 (rc1) release tracking the recent release of
Apache Lucene 7.7.1 is ready.
A release candidate is available from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/7.7.1-rc1/
PyLucene 7.7.1 is built with JCC 3.5, included in these release artifacts.
JCC 3.5 supports Python 3.3+ (in addition to Python 2.3+).
PyLucene may be built with Python 2 or Python 3.
Please vote to release these artifacts as PyLucene 7.7.1.
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
Re: [VOTE] Release PyLucene 8.1.1
Posted by Jan Høydahl <ja...@cominvent.com>.
https://www.apache.org/foundation/voting.html
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 11. jun. 2019 kl. 15:30 skrev David Allouche <da...@allouche.net>:
>
> This is maybe a silly question, but what is the purpose of this voting process?
>
> Is this something required by the project governance?
>
> What is the meaning of a vote? Does that mean "I am interested", or does it mean "I have tested the latest trunk and it looks good", or something else?
>
> What is the typical expected delay for reply? For example, I reserve Fridays for technical debt management (including upgrading dependencies), so I cannot typically validate a new PyLucene version in less than a week.
>
> This is probably all common questions with well documented answers. If that's the case, then it would be nice to have a link to the answers in VOTE requests.
>
>> On 11 Jun 2019, at 00:39, Andi Vajda <va...@apache.org> wrote:
>>
>>
>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
>> Apache Lucene 8.1.1 is ready.
>>
>> A release candidate is available from:
>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>>
>> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>>
>> JCC 3.5 supports Python 3.3+ (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.1.1.
>> 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
>
Re: [VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
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:
>> <5c...@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.
>
Re: [VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
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: <5c...@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.
Re: [VOTE] Release PyLucene 8.1.1
Posted by David Allouche <da...@allouche.net>.
> 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.
Message-Id: <5c...@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.
RE: [VOTE] Release PyLucene 8.1.1
Posted by Milo H Fields III <mf...@paladin-sys.com>.
+0 (user)
> -----Original Message-----
> From: Andi Vajda <va...@apache.org>
> Sent: Monday, June 17, 2019 14:43
> To: pylucene-dev@lucene.apache.org
> Subject: Re: [VOTE] Release PyLucene 8.1.1
>
>
> 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.
>
> Besides the Apache procedural aspect, voting is also a gauge of interest
in a
> project. If there is no user interest in the PyLucene project anymore
maybe
> it's time to stop making releases for a while ?
>
> PyLucene is a bit special in that it doesn't involve many people for
> development since it is machine-generated by JCC and JCC has been stable
> for a while. In that sense, it is important that actual users of PyLucene
make
> themselves known by voting, not much else goes on on the project's mailing
> list or in the source code.
>
> If there are actual users showing interest by voting here, I feel more
> confortable then in nagging people on the Lucene PMC for their procedural
> vote.
>
> Andi..
>
> >
> > I will post my questions about index upgrading on
> > java-user@lucene.apache.org <ma...@lucene.apache.org>.
>
>
> >
> > Regards.
> >
> >> On 11 Jun 2019, at 16:50, Andi Vajda <va...@apache.org> wrote:
> >>
> >>
> >>> On Jun 11, 2019, at 06:30, David Allouche <da...@allouche.net> wrote:
> >>>
> >>> This is maybe a silly question, but what is the purpose of this voting
> process?
> >>
> >> By the rules of Apache, three PMC binding votes are needed to make a
> release. In addition, it's a gauge of general interest in the project.
> >>
> >>> Is this something required by the project governance?
> >>
> >> https://www.apache.org/foundation/voting.html
> >> (see "votes on package releases", in particular)
> >>
> >>> What is the meaning of a vote? Does that mean "I am interested", or
> does it mean "I have tested the latest trunk and it looks good", or
something
> else?
> >>
> >> If you find a bug in the release artifacts (not in the latest trunk)
before the
> release is made, the release is likely to be pulled.
> >>
> >>> What is the typical expected delay for reply? For example, I reserve
> Fridays for technical debt management (including upgrading dependencies),
> so I cannot typically validate a new PyLucene version in less than a week.
> >>
> >> A vote must run for at least 72 hours.
> >> Because you are not on the PMC, your vote falls into the "interest
> gauging" category, is not binding and is considered "best effort".
> >>
> >>> This is probably all common questions with well documented answers. If
> that's the case, then it would be nice to have a link to the answers in
VOTE
> requests.
> >>
> >> https://www.apache.org/foundation/voting.html
> >>
> >> Andi..
> >>
> >>>
> >>>> On 11 Jun 2019, at 00:39, Andi Vajda <va...@apache.org> wrote:
> >>>>
> >>>>
> >>>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
> >>>> Apache Lucene 8.1.1 is ready.
> >>>>
> >>>> A release candidate is available from:
> >>>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
> >>>>
> >>>> PyLucene 8.1.1 is built with JCC 3.5, included in these release
artifacts.
> >>>>
> >>>> JCC 3.5 supports Python 3.3+ (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.1.1.
> >>>> 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
> >>>
> >
> >
Re: [VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
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.
Besides the Apache procedural aspect, voting is also a gauge of interest in
a project. If there is no user interest in the PyLucene project anymore
maybe it's time to stop making releases for a while ?
PyLucene is a bit special in that it doesn't involve many people for
development since it is machine-generated by JCC and JCC has been stable for
a while. In that sense, it is important that actual users of PyLucene make
themselves known by voting, not much else goes on on the project's mailing
list or in the source code.
If there are actual users showing interest by voting here, I feel more
confortable then in nagging people on the Lucene PMC for their procedural
vote.
Andi..
>
> I will post my questions about index upgrading on
> java-user@lucene.apache.org <ma...@lucene.apache.org>.
>
> Regards.
>
>> On 11 Jun 2019, at 16:50, Andi Vajda <va...@apache.org> wrote:
>>
>>
>>> On Jun 11, 2019, at 06:30, David Allouche <da...@allouche.net> wrote:
>>>
>>> This is maybe a silly question, but what is the purpose of this voting process?
>>
>> By the rules of Apache, three PMC binding votes are needed to make a release. In addition, it's a gauge of general interest in the project.
>>
>>> Is this something required by the project governance?
>>
>> https://www.apache.org/foundation/voting.html
>> (see "votes on package releases", in particular)
>>
>>> What is the meaning of a vote? Does that mean "I am interested", or does it mean "I have tested the latest trunk and it looks good", or something else?
>>
>> If you find a bug in the release artifacts (not in the latest trunk) before the release is made, the release is likely to be pulled.
>>
>>> What is the typical expected delay for reply? For example, I reserve Fridays for technical debt management (including upgrading dependencies), so I cannot typically validate a new PyLucene version in less than a week.
>>
>> A vote must run for at least 72 hours.
>> Because you are not on the PMC, your vote falls into the "interest gauging" category, is not binding and is considered "best effort".
>>
>>> This is probably all common questions with well documented answers. If that's the case, then it would be nice to have a link to the answers in VOTE requests.
>>
>> https://www.apache.org/foundation/voting.html
>>
>> Andi..
>>
>>>
>>>> On 11 Jun 2019, at 00:39, Andi Vajda <va...@apache.org> wrote:
>>>>
>>>>
>>>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
>>>> Apache Lucene 8.1.1 is ready.
>>>>
>>>> A release candidate is available from:
>>>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>>>>
>>>> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>>>>
>>>> JCC 3.5 supports Python 3.3+ (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.1.1.
>>>> 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
>>>
>
>
Re: [VOTE] Release PyLucene 8.1.1
Posted by David Allouche <da...@allouche.net>.
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.
I will post my questions about index upgrading on java-user@lucene.apache.org <ma...@lucene.apache.org>.
Regards.
> On 11 Jun 2019, at 16:50, Andi Vajda <va...@apache.org> wrote:
>
>
>> On Jun 11, 2019, at 06:30, David Allouche <da...@allouche.net> wrote:
>>
>> This is maybe a silly question, but what is the purpose of this voting process?
>
> By the rules of Apache, three PMC binding votes are needed to make a release. In addition, it's a gauge of general interest in the project.
>
>> Is this something required by the project governance?
>
> https://www.apache.org/foundation/voting.html
> (see "votes on package releases", in particular)
>
>> What is the meaning of a vote? Does that mean "I am interested", or does it mean "I have tested the latest trunk and it looks good", or something else?
>
> If you find a bug in the release artifacts (not in the latest trunk) before the release is made, the release is likely to be pulled.
>
>> What is the typical expected delay for reply? For example, I reserve Fridays for technical debt management (including upgrading dependencies), so I cannot typically validate a new PyLucene version in less than a week.
>
> A vote must run for at least 72 hours.
> Because you are not on the PMC, your vote falls into the "interest gauging" category, is not binding and is considered "best effort".
>
>> This is probably all common questions with well documented answers. If that's the case, then it would be nice to have a link to the answers in VOTE requests.
>
> https://www.apache.org/foundation/voting.html
>
> Andi..
>
>>
>>> On 11 Jun 2019, at 00:39, Andi Vajda <va...@apache.org> wrote:
>>>
>>>
>>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
>>> Apache Lucene 8.1.1 is ready.
>>>
>>> A release candidate is available from:
>>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>>>
>>> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>>>
>>> JCC 3.5 supports Python 3.3+ (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.1.1.
>>> 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
>>
Re: [VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
> On Jun 11, 2019, at 06:30, David Allouche <da...@allouche.net> wrote:
>
> This is maybe a silly question, but what is the purpose of this voting process?
By the rules of Apache, three PMC binding votes are needed to make a release. In addition, it's a gauge of general interest in the project.
> Is this something required by the project governance?
https://www.apache.org/foundation/voting.html
(see "votes on package releases", in particular)
> What is the meaning of a vote? Does that mean "I am interested", or does it mean "I have tested the latest trunk and it looks good", or something else?
If you find a bug in the release artifacts (not in the latest trunk) before the release is made, the release is likely to be pulled.
> What is the typical expected delay for reply? For example, I reserve Fridays for technical debt management (including upgrading dependencies), so I cannot typically validate a new PyLucene version in less than a week.
A vote must run for at least 72 hours.
Because you are not on the PMC, your vote falls into the "interest gauging" category, is not binding and is considered "best effort".
> This is probably all common questions with well documented answers. If that's the case, then it would be nice to have a link to the answers in VOTE requests.
https://www.apache.org/foundation/voting.html
Andi..
>
>> On 11 Jun 2019, at 00:39, Andi Vajda <va...@apache.org> wrote:
>>
>>
>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
>> Apache Lucene 8.1.1 is ready.
>>
>> A release candidate is available from:
>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>>
>> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>>
>> JCC 3.5 supports Python 3.3+ (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.1.1.
>> 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
>
Re: [VOTE] Release PyLucene 8.1.1
Posted by David Allouche <da...@allouche.net>.
This is maybe a silly question, but what is the purpose of this voting process?
Is this something required by the project governance?
What is the meaning of a vote? Does that mean "I am interested", or does it mean "I have tested the latest trunk and it looks good", or something else?
What is the typical expected delay for reply? For example, I reserve Fridays for technical debt management (including upgrading dependencies), so I cannot typically validate a new PyLucene version in less than a week.
This is probably all common questions with well documented answers. If that's the case, then it would be nice to have a link to the answers in VOTE requests.
> On 11 Jun 2019, at 00:39, Andi Vajda <va...@apache.org> wrote:
>
>
> The PyLucene 8.1.1 (rc1) release tracking the recent release of
> Apache Lucene 8.1.1 is ready.
>
> A release candidate is available from:
> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>
> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>
> JCC 3.5 supports Python 3.3+ (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.1.1.
> 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
RE: [VOTE] Release PyLucene 8.1.1
Posted by Marc Jeurissen <ma...@uantwerpen.be>.
+1
Met vriendelijke groeten,
Marc Jeurissen
Bibliotheek UAntwerpen
Stadscampus – Ve35.303
Venusstraat 35 – 2000 Antwerpen
marc.jeurissen@uantwerpen.be
T +32 3 265 49 71
From: Andi Vajda
Sent: dinsdag 11 juni 2019 0:40
To: Andi Vajda
Cc: pylucene-dev@lucene.apache.org; general@lucene.apache.org
Subject: [VOTE] Release PyLucene 8.1.1
The PyLucene 8.1.1 (rc1) release tracking the recent release of
Apache Lucene 8.1.1 is ready.
A release candidate is available from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
JCC 3.5 supports Python 3.3+ (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.1.1.
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
Re: [VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
> On Jun 10, 2019, at 22:24, Victor Olaiya <vi...@gmail.com> wrote:
>
> Okay thanks,
> I tried building it, I was getting errors of org.apache.x.x.jar not found.
> I was building using maven.
> Although I haven't installed the main lucene I just have it downloaded and
> unarchived.
>
> Do I have to build it form the lucene directory for it to work?
I don't know.
> How then do I integrate it with my indexes.
I don't know. What does it mean to use Luke from python anyway ? Isn't the Java interface sufficient ?
(your PyLucene indexes should be fully compatible with Java Lucene ones, of course, it's Java Lucene doing all the work in both cases).
Anyhow, you should ask all Luke-related questions on the lunene user list:
http://lucene.apache.org/core/discussion.html
Andi..
>
>> On Tue, 11 Jun 2019, 6:21 am Andi Vajda <vajda@apache.org wrote:
>>
>>
>>> On Jun 10, 2019, at 22:06, Victor Olaiya <vi...@gmail.com> wrote:
>>>
>>> Thank you Andi,😋
>>> does it come with luke preinstalled?
>>
>> Not really. It can be built but seems to be very slow to load so it should
>> be built as a separate module from the main lucene one.
>>
>> Andi..
>>
>>>
>>>> On Mon, Jun 10, 2019 at 11:39 PM Andi Vajda <va...@apache.org> wrote:
>>>>
>>>>
>>>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
>>>> Apache Lucene 8.1.1 is ready.
>>>>
>>>> A release candidate is available from:
>>>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>>>>
>>>> PyLucene 8.1.1 is built with JCC 3.5, included in these release
>> artifacts.
>>>>
>>>> JCC 3.5 supports Python 3.3+ (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.1.1.
>>>> 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
>>>>
>>
>>
Re: [VOTE] Release PyLucene 8.1.1
Posted by Victor Olaiya <vi...@gmail.com>.
Okay thanks,
I tried building it, I was getting errors of org.apache.x.x.jar not found.
I was building using maven.
Although I haven't installed the main lucene I just have it downloaded and
unarchived.
Do I have to build it form the lucene directory for it to work?
How then do I integrate it with my indexes.
On Tue, 11 Jun 2019, 6:21 am Andi Vajda <vajda@apache.org wrote:
>
> > On Jun 10, 2019, at 22:06, Victor Olaiya <vi...@gmail.com> wrote:
> >
> > Thank you Andi,😋
> > does it come with luke preinstalled?
>
> Not really. It can be built but seems to be very slow to load so it should
> be built as a separate module from the main lucene one.
>
> Andi..
>
> >
> >> On Mon, Jun 10, 2019 at 11:39 PM Andi Vajda <va...@apache.org> wrote:
> >>
> >>
> >> The PyLucene 8.1.1 (rc1) release tracking the recent release of
> >> Apache Lucene 8.1.1 is ready.
> >>
> >> A release candidate is available from:
> >> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
> >>
> >> PyLucene 8.1.1 is built with JCC 3.5, included in these release
> artifacts.
> >>
> >> JCC 3.5 supports Python 3.3+ (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.1.1.
> >> 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
> >>
>
>
Re: [VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
> On Jun 10, 2019, at 22:06, Victor Olaiya <vi...@gmail.com> wrote:
>
> Thank you Andi,😋
> does it come with luke preinstalled?
Not really. It can be built but seems to be very slow to load so it should be built as a separate module from the main lucene one.
Andi..
>
>> On Mon, Jun 10, 2019 at 11:39 PM Andi Vajda <va...@apache.org> wrote:
>>
>>
>> The PyLucene 8.1.1 (rc1) release tracking the recent release of
>> Apache Lucene 8.1.1 is ready.
>>
>> A release candidate is available from:
>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>>
>> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>>
>> JCC 3.5 supports Python 3.3+ (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.1.1.
>> 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
>>
Re: [VOTE] Release PyLucene 8.1.1
Posted by Victor Olaiya <vi...@gmail.com>.
Thank you Andi,😋
does it come with luke preinstalled?
On Mon, Jun 10, 2019 at 11:39 PM Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 8.1.1 (rc1) release tracking the recent release of
> Apache Lucene 8.1.1 is ready.
>
> A release candidate is available from:
> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
>
> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
>
> JCC 3.5 supports Python 3.3+ (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.1.1.
> 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
>
[VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 8.1.1 (rc1) release tracking the recent release of
Apache Lucene 8.1.1 is ready.
A release candidate is available from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
JCC 3.5 supports Python 3.3+ (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.1.1.
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
[VOTE] Release PyLucene 8.1.1
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 8.1.1 (rc1) release tracking the recent release of
Apache Lucene 8.1.1 is ready.
A release candidate is available from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/
PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts.
JCC 3.5 supports Python 3.3+ (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.1.1.
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