Hi,

Here is a guide of how to vote [1]. And yes, we need to invite more active 
PPMCs :).

[1] http://iotdb.apache.org/Development/VoteRelease.html

Thanks,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -----原始邮件-----
> 发件人: "Dawei Liu" <[email protected]>
> 发送时间: 2020-05-11 20:59:19 (星期一)
> 收件人: dev <[email protected]>
> 抄送: "[email protected]" <[email protected]>
> 主题: Re: [RESULT] [VOTE] Apache IoTDB 0.9.3 (Incubating) RC1 release
> 
> Hi Christofer,
> You are absolutely right. 
> 
> 
> 1. We should encourage and teach more people how to vote
> 
> ?. We should consider whether to add more active people to become PPMC.
> 
> 
> Thanks
> ———
> Dawei Liu
> 
> 
> On 05/11/2020 20:14, Christofer Dutz wrote:
> Hi all,
> 
> I just wanted to point out that if so few active PPMCs are voting, this could 
> be an issue ...
> Perhaps it's worth discussing to invite fresh PPMCs in.
> 
> With PLC4X it was pretty similar situation. We had a big list of initial 
> committers and PPMCs.
> When approaching graduation we simply voted to list only those PPMCs as 
> Initial PMC for the TLP that actively expressed the wish to do so.
> 
> I would just like to encourage everyone to actively help checking release 
> candidates. Also the committers or not even committers.
> Even if your vote formally doesn't count, it usually does count. And it 
> definitely usually helps getting voted in PPMC for most projects ;-)
> 
> Chris
> 
> 
> 
> 
> 
> 
> Am 11.05.20, 05:58 schrieb "Justin Mclean" <[email protected]>:
> 
>    Hi,
> 
> 
>    Only 3 +1 votes are needed (and more +1’s than -1) to make a release. It 
> is good if more people look at it as they may catch something the others 
> missed. Most votes on release only get 3-5 votes so that’s fine.
> 
>    Re the PPMC this can be adjusted on graduation, it’s usually done by 
> asking existing PPMC members if they want to be on the PMC of the TLP 
> project. Having inactive (P)PMC members is not a big issues and they may be 
> active again at some point in the future.
> 
>    Thanks,
>    Justin
> 

Reply via email to