Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAKJfLDNLpONBPJJEq2tB+qAr=f-arGLsjHRSmG=nVAi3sti7kA@mail.gmail.com>
References: <9B661F7E-F6F7-45A7-86C7-3E362DB71B63@classsoftware.com>
 <CAKJfLDPY76_YD9jM2bPzenPRVhpxUNCR6b=zPDnEUafBWwk88w@mail.gmail.com>
 <333169E2-A1B8-42C4-AAB6-7723E7F4A185@classsoftware.com>
 <CAKJfLDNLpONBPJJEq2tB+qAr=f-arGLsjHRSmG=nVAi3sti7kA@mail.gmail.com>
From: Ted Dunning <ted.dunning@gmail.com>
Date: Tue, 17 Nov 2015 12:53:03 +0900
Message-ID: 
 <CAJwFCa1-oEL_7S56p2EwFMrpu4VX9Ffu+u-5pRoTwX6f-RDWqg@mail.gmail.com>
Subject: Re: Incubator vote for Malhar release
To: dev@apex.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a1141fac838f0fa0524b47812

--001a1141fac838f0fa0524b47812
Content-Type: text/plain; charset=UTF-8

On Tue, Nov 17, 2015 at 9:47 AM, Thomas Weise <thomas@datatorrent.com>
wrote:

> Thanks. We have 3 binding votes so we are good with this release.
>
> Also wanted to know if the voting can be expedited for future releases (now
> that we have the basic release kinks worked out).
>


The issue with this is that expediting the voting means that IPMC members
who would like to review a release but who are not on your dev list are
effectively disenfranchised by a short vote cycle.

As Justin suggested, the answer is to graduate. It won't be that long
before that happens, I would guess.  Making clean releases that have been
well examined is really key to that.


> Is there an option to combine PPMC and IPMC vote and let everyone vote on
> general@ ? In the end, that's the ultimate vote and only IPMC votes are
> binding.
>

Having the community vote separately is viewed by many as useful since it
is closer to the way the vote will eventually proceed when the project
becomes independent of the incubator.

--001a1141fac838f0fa0524b47812--