On Apr 24, 2014, at 11:40 AM, Andi Vajda <va...@apache.org> wrote: > On Thu, 24 Apr 2014, Thomas Koch wrote: >> I don't agree that it is unimportant to make PyLucene releases. Without a >> ready-to-run software package the hurdles to use PyLucene are raised. It is >> already not quite simple (for beginners) to install PyLucene on the various >> platforms. Having a packaged release that is tested by some users provides a >> benefit to the community in my opinion. > > I agree with you that making releases is important. However, when votes are > called to actually make them, it's been hard to get voters to respond. > > Anyone can vote. Anyone with an interest should vote. Three PMC votes are > required to make a release happen, though. But any vote for or against is > important, PMC or not. Lately, it's been hard to get the TWO extra PMC votes > needed to make a release happen (since mine is cast when I cut the release > candidate). I think this is in part _because_ no one else is showing an > interest in the release and casting a vote either.
Oh, well I for one had no idea votes from the community at large were encouraged. In that case… +1. I tested 4.7.2 against my downstream project. No issues. >> However I can understand your arguments - there has been little feedback on >> your release announcements on the list recently. On the other hand there are >> frequent discussions about PyLucene on the list so I don't think the >> interest has declined. Did you check the number of downloads of the PyLucene >> distributions (if this is possible at all - due to the distributed releases >> on the apache mirrors ...)? This would be a more accurate indicator from my >> point of view. > > I have no idea about the number of downloads of PyLucene. JCC, however, has > gotten over 2700 downloads in the past month: > https://pypi.python.org/pypi/JCC/2.19 > >> I must also admit that I did never understand the voting process in detail - >> i.e. who are the PMC members and what impact have votes of non PMC users. >> Maybe some more transparency and another "call for action" would help to >> raise awareness in the community. > > There are at least three classes in the Apache meritocracy: > - users, developers, contributors but not committers > - committers, ie developers who can commit patches to the project > - PMC members, ie project committers that sit on the PMC (project > management committee) > For more information, please see: > https://www.apache.org/foundation/how-it-works.html > > By the rules guiding the release of Apache projects, three PMC votes are > necessary to release a tarball to the world. > The list of Lucene committers is visible here: > http://lucene.apache.org/whoweare.html > Scroll down that list for the PMC membership. > > Andi..
