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
