----- Original Message ----
> From: sebb <seb...@gmail.com>
> To: general@incubator.apache.org
> Sent: Friday, August 21, 2009 10:15:44 AM
> Subject: Re: Making up policy on the fly
>
> On 21/08/2009, Joe Schaefer wrote:
> > ----- Original Message ----
> >
> > > From: ant elder
> > > To: general@incubator.apache.org
> >
> > > Sent: Friday, August 21, 2009 2:32:39 AM
> > > Subject: Re: Making up policy on the fly
> >
> >
> > > Several improvements have been suggested on this thread so far, the
> > > two mains ones are:
> > >
> > > - hold the release votes on the poddling mailing lists not general@
> >
> >
> > At one point or another I thought that might be an improvement. Having
> > seen how many podling releases fail to pass the vote on gene...@incubator
> > has me thinking otherwise. Until the gene...@incubator votes are little
> > more than rubber stamps of the votes conducted on the podling's dev list, I
> > wouldn't be in favor of such a change.
> >
>
> The votes that count for a release are IPMC member votes; seems to me
> that the vote must be put to the whole IPMC, even if most of them
> don't vote. If the vote were only on the podling list, then only IPMC
> members who happened to be on the list would see the vote - the other
> IPMC members would effectively be disenfranchised.
>
> The IPMC might as well be disbanded at that point.
Well that's the way things are done in other TLPs with subprojects: the
vote on the subproject's candidates is carried out on the subproject's dev
list. But I can see your point, especially because these podlings really
don't map to subprojects.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
