RE: [VOTE] Release PyLucene 8.1.1

2019-06-17 Thread Milo H Fields III 
+0 (user)


> -Original Message-
> From: Andi Vajda 
> 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-u...@lucene.apache.org .
> 
> 
> >
> > Regards.
> >
> >> On 11 Jun 2019, at 16:50, Andi Vajda  wrote:
> >>
> >>
> >>> On Jun 11, 2019, at 06:30, David Allouche  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  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
> >>>
> >
> >


smime.p7s
Description: S/MIME cryptographic signature

RE: Unit Test Question - test_Collections.py

2018-02-12 Thread Milo H. Fields III 
No worries 
-- we are testing pylucene against original delivery in Windows, RHEL7 and 
CentOS 7 as we support these platforms and have started integration of pylucene 
& lucene/tika into our business logic/CIE systems..
We target python3 but I will make sure the changes can be reflected in the 
python2 unit tests as well.. I'll let you know when I something ready.  

I'm working off the SVN trunk and assume you prefer a diff patch set..

> -Original Message-
> From: Andi Vajda [mailto:va...@apache.org]
> Sent: Monday, February 12, 2018 13:01
> To: pylucene-dev@lucene.apache.org
> Subject: Re: Unit Test Question - test_Collections.py
> 
> 
> > On Feb 12, 2018, at 09:33, Milo H. Fields III <mfie...@paladin-sys.com>
> wrote:
> >
> > Andi,
> > I have integrated PyLucene into a Visual Studio 2017 project space including
> support for VS Python unit test fixture (AKA Test Explorer) and other IDE
> platforms we use that instrument the unit test sets. This required some
> minor tweaking to the test classes to support running the test suite
> independent of a command line '__main__' (example below).
> > 
> > # PyLuceneTestCase.py  class PyLuceneTestCase #line 32 Method __init__
> > is:
> >def __init__(self, *args):
> >super(PyLuceneTestCase, self).__init__(*args)
> >
> > # changed to:
> >def __init__(self, *args):
> >super(PyLuceneTestCase, self).__init__(*args)
> >if not lucene.getVMEnv():
> >lucene.initVM(vmargs=['-Djava.awt.headless=true'])
> > -
> > If you would be interesting in supporting the modifications to the unit test
> fixtures I will submit them for review & test.
> 
> If you send me a patch, I’ll integrate it after checking that it doesn’t 
> break the
> ‘usual’ way of running tests. As I don’t have access to Windows, I can’t test
> your fix for its intent nor verify that later changes won’t accidentally 
> break it.
> 
> Thank you !
> 
> Andi..
> 
> >
> > v/r
> > milo..
> >
> >> -Original Message-
> >> From: Andi Vajda [mailto:va...@apache.org]
> >> Sent: Saturday, February 10, 2018 20:53
> >> To: pylucene-dev@lucene.apache.org
> >> Subject: Re: Unit Test Question - test_Collections.py
> >>
> >> Yes, that looks like a copy/paste error indeed.
> >> Thank you for reporting this.
> >>
> >> Andi..
> >>
> >>> On Feb 10, 2018, at 14:52, Milo H. Fields III
> >>> <mfie...@paladin-sys.com>
> >> wrote:
> >>>
> >>> # pylucene-7.2.0\test3\test_Collections.py
> >>> # line 109
> >>> class Test_CollectionsBoolList(Test_CollectionsSetBase):
> >>>
> >>>def createTestSet(self):
> >>>return set([True,False])
> >>>
> >>> # then at line 248
> >>> class Test_CollectionsBoolList(Test_CollectionsListBase):
> >>>
> >>>def createTestList(self):
> >>>return [True,False]
> >>>
> >>>
> >>> # Shouldn’t the first instance be named?
> >>> class Test_CollectionsBoolSet(Test_CollectionsSetBase):
> >>>
> >>> It causes issues for the python3.6.4 running on Windows 10
> >>>
> >>>
> >>>

RE: Unit Test Question - test_Collections.py

2018-02-12 Thread Milo H. Fields III 
Andi,
I have integrated PyLucene into a Visual Studio 2017 project space including 
support for VS Python unit test fixture (AKA Test Explorer) and other IDE 
platforms we use that instrument the unit test sets. This required some minor 
tweaking to the test classes to support running the test suite independent of a 
command line '__main__' (example below). 

# PyLuceneTestCase.py  class PyLuceneTestCase
#line 32 Method __init__ is:
def __init__(self, *args):
super(PyLuceneTestCase, self).__init__(*args)

# changed to:
def __init__(self, *args):
super(PyLuceneTestCase, self).__init__(*args)
if not lucene.getVMEnv():
lucene.initVM(vmargs=['-Djava.awt.headless=true'])
-
If you would be interesting in supporting the modifications to the unit test 
fixtures I will submit them for review & test.

v/r
milo..

> -Original Message-
> From: Andi Vajda [mailto:va...@apache.org]
> Sent: Saturday, February 10, 2018 20:53
> To: pylucene-dev@lucene.apache.org
> Subject: Re: Unit Test Question - test_Collections.py
> 
> Yes, that looks like a copy/paste error indeed.
> Thank you for reporting this.
> 
> Andi..
> 
> > On Feb 10, 2018, at 14:52, Milo H. Fields III <mfie...@paladin-sys.com>
> wrote:
> >
> > # pylucene-7.2.0\test3\test_Collections.py
> > # line 109
> > class Test_CollectionsBoolList(Test_CollectionsSetBase):
> >
> > def createTestSet(self):
> > return set([True,False])
> >
> > # then at line 248
> > class Test_CollectionsBoolList(Test_CollectionsListBase):
> >
> > def createTestList(self):
> > return [True,False]
> >
> >
> > # Shouldn’t the first instance be named?
> > class Test_CollectionsBoolSet(Test_CollectionsSetBase):
> >
> > It causes issues for the python3.6.4 running on Windows 10
> >
> >
> >


smime.p7s
Description: S/MIME cryptographic signature

Unit Test Question - test_Collections.py

2018-02-10 Thread Milo H. Fields III 
# pylucene-7.2.0\test3\test_Collections.py 

# line 109 

class Test_CollectionsBoolList(Test_CollectionsSetBase):

 

def createTestSet(self):

return set([True,False])

 

# then at line 248

class Test_CollectionsBoolList(Test_CollectionsListBase):

 

def createTestList(self):

return [True,False]

 

 

# Shouldn't the first instance be named?

class Test_CollectionsBoolSet(Test_CollectionsSetBase):

 

It causes issues for the python3.6.4 running on Windows 10

 

 

 



smime.p7s
Description: S/MIME cryptographic signature

RE: [nag][VOTE] Release PyLucene 7.2.0 (rc1)

2018-01-08 Thread Milo H. Fields III 
Please excuse my ignorance of Apache process -- 'who/what' are PCM's?  
I've built and am have been using on Win10 against Py3.6.4 & Py2.7.14  (jdk
1.8.0_152) without issue

v/r

> -Original Message-
> From: Petrus Hyvönen [mailto:petrus.hyvo...@gmail.com]
> Sent: Monday, January 8, 2018 08:24
> To: pylucene-dev@lucene.apache.org
> Cc: gene...@lucene.apache.org
> Subject: Re: [nag][VOTE] Release PyLucene 7.2.0 (rc1)
> 
> Just to encourage, Please PMC's vote so we can have a fresh release of JCC
> also!
> 
> Many Thanks for you efforts,
> /Petrus
> 
> 
> > On 4 Jan 2018, at 11:29 , Andi Vajda  wrote:
> >
> >
> > Two more PMC votes are needed to make this release !
> > Thanks !
> >
> > -- Forwarded message --
> > Date: Thu, 21 Dec 2017 03:50:08 -0800 (PST)
> > From: Andi Vajda 
> > To: pylucene-dev@lucene.apache.org
> > Cc: gene...@lucene.apache.org
> > Subject: [VOTE] Release PyLucene 7.2.0 (rc1)
> >
> >
> > The PyLucene 7.2.0 (rc1) release tracking the upcoming release of
> > Apache Lucene 7.2.0 is ready.
> >
> > A release candidate is available from:
> >  https://dist.apache.org/repos/dist/dev/lucene/pylucene/7.2.0-rc1/
> >
> > PyLucene 7.2.0 is built with JCC 3.1 included in these release
artifacts.
> >
> > JCC 3.1 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.2.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



smime.p7s
Description: S/MIME cryptographic signature