Another solution is to do back door politicking where you contact IPMC members individually and ask them to take a look. Start with members who have voted on Mahout releases in the past and be specific about what you would like them do and provide links to artifacts and discussions to make the job easy.
That has usually been my best way to succeed on that. On Sat, Apr 22, 2017 at 10:19 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > That works if human nature is not involved and would still produce the > same affect so I’d second your request in any case. > > However human nature is involved and my proposal would at least guarantee > that human nature could not hold innocent projects hostage. BTW notice the > include vote request, now over a week in with no binding up or down votes. > > > On Apr 22, 2017, at 10:02 AM, Julian Hyde <jh...@apache.org> wrote: > > I agree that lack of IPMC votes is a problem. I don’t think that lowering > the bar to making a release is the solution. > > I wish that each IPMC member would personally commit to voting on two > release candidates per year. There are so many members of the IPMC that > this would easily cover all of the votes that come up. > > Julian > > > > On Apr 22, 2017, at 8:46 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > > > > Probably the wrong place for this but… > > > > What do people think about a governance change for approving releases > through the IPMC to wit: > > > > A week of no vote activity over the release proposal of a podling should > be considered a passing vote. In other words the IPMC is to become a > vetoing group. > > > > I propose this for 2 reasons: 1) lack of votes or attention from the > IPMC seems all too prevalent and puts an undo drag on the energy and > velocity of community involvement. 2) the release has already been voted on > and checked by at least 3 PMC members of the podling (which has ASF mentors > in most all cases) so a veto role by the IPMC seems to have minimum danger > to the ASF system of checks and balances. > > > > > > > > > > On Apr 19, 2017, at 9:33 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > > > > +1 non-binding > > > > Next release we could exclude the doc site. Do build files like .sbt > require licenses? I suppose it can be done in comments. But again can we > push to next release > > > > Can other binding voters have a look? I know everyone is busy but hey, > tax day is past ;-) > > > > > > On Apr 18, 2017, at 1:00 PM, Donald Szeto <don...@apache.org> wrote: > > > > Hi Luciano, > > > > Thanks for your review. I will file JIRAs regarding these files. They are > > project build files and documentation. > > > > Regards, > > Donald > > > > On Mon, Apr 17, 2017 at 1:29 PM, Luciano Resende <luckbr1...@gmail.com> > > wrote: > > > >> On Thu, Apr 13, 2017 at 11:41 AM, Donald Szeto <don...@apache.org> > wrote: > >> > >>> Hi all, > >>> > >>> The PredictionIO community has voted that 0.11.0-incubating-rc2 to be > >> good > >>> for a source-only release. This thread is to facilitate a voting for > the > >>> IPMC before a final official source-only release. > >>> > >>> Vote result on dev@: > >>> https://lists.apache.org/thread.html/031ff6f98b3d5a54b716789bda5068 > >>> 1a0c821f1054218843ac5fcc77@%3Cdev.predictionio.apache.org%3E > >>> > >>> The original vote thread on dev@: > >>> https://lists.apache.org/thread.html/d1bf205404bf4e16e12f17209f4f20 > >>> 7722e554ee9e4139974812f8e4@%3Cdev.predictionio.apache.org%3E > >>> > >>> The release candidate Git commit is: > >>> e34a853d0e89baed09b3d3b0c25b244162a3bdea > >>> > >>> The release candidate Git tag is: > >>> v0.11.0-incubating-rc2 > >>> > >>> The source-only release candidate artifacts can be downloaded here: > >>> https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.11.0- > >>> incubating-rc2/ > >>> > >>> Test results of RC2 can be found here: > >>> https://travis-ci.org/apache/incubator-predictionio/builds/220381611 > >>> > >>> Build instructions of previous versions can be used on this RC: > >>> http://predictionio.incubator.apache.org/install/install-sourcecode/ > >>> > >>> Maven artifacts are built from the release candidate artifacts above, > and > >>> are provided as convenience for testing with PredictionIO engine > >> templates. > >>> The Maven artifacts are provided at the Maven staging repo here: > >>> https://repository.apache.org/content/repositories/ > >>> orgapachepredictionio-1016/ > >>> > >>> All JIRAs completed for this release are tagged with 'FixVersion = > >>> 0.11.0-incubating'. You can view them here: > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > >>> projectId=12320420&version=12338381 > >>> > >>> The artifacts have been signed with Key : 8BF4ABEB > >>> > >>> Please vote accordingly: > >>> > >>> [ ] +1, accept RC as the official 0.11.0 release > >>> [ ] 0, neutral because... > >>> [ ] -1, do not accept RC as the official 0.11.0 release because... > >>> > >>> The vote will be open for 72 hours and close at 12pm PDT 4/16/2016. > >>> > >>> Regards, > >>> Donald > >>> > >> > >> > >> I was running RAT on the source distribution and there are a lot of > unknown > >> licenses, some might be ok, but many are not, such as: > >> > >> *.sbt in projects and sub-projects > >> *.css in docs > >> > >> Other things like signatures, etc seems ok > >> > >> > >> > >> -- > >> Luciano Resende > >> http://twitter.com/lresende1975 > >> http://lresende.blogspot.com/ > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
