You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Craig Russell <ap...@gmail.com> on 2019/04/01 03:30:35 UTC
[DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
This is a proposal to recommend that all Mentors SHOULD vote on podling releases prior to sending the release for a vote to the IPMC.
This is not a MUST, since there are many good reasons why a mentor might be unable to perform the checks needed to vote. We are volunteers after all.
But if this proposal is adopted, it will minimize the occurrences of a podling desperately asking for someone, anyone, on the IPMC to please vote.
It should also minimize the number of podling releases that are shot down in the full IPMC vote because of something that a Mentor is likely to catch.
Thanks for your consideration,
Craig
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
Directly on this proposal, I agree. In Zipkin (incubating) we are lucky
that mentors are already active.
However, we should not take this for granted and certainly it would be
harder and more fragile if our mentors were not looking carefully and
voting.
-A
On Mon, Apr 1, 2019, 10:30 AM Craig Russell <ap...@gmail.com> wrote:
> This is a proposal to recommend that all Mentors SHOULD vote on podling
> releases prior to sending the release for a vote to the IPMC.
>
> This is not a MUST, since there are many good reasons why a mentor might
> be unable to perform the checks needed to vote. We are volunteers after all.
>
> But if this proposal is adopted, it will minimize the occurrences of a
> podling desperately asking for someone, anyone, on the IPMC to please vote.
>
> It should also minimize the number of podling releases that are shot down
> in the full IPMC vote because of something that a Mentor is likely to catch.
>
> Thanks for your consideration,
>
> Craig
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by ba...@tobin.nl.
Sorry Justin but this is you looking for “problems” that just are not there and to me it comes across as you taking joy out of frustrating people. Nothing about “nagging mentors privately to vote” holds any additional / relevant information that needs disclosure to the public.
So something needs to be done AND this CTA has been advertised in public and we all want to move things forward. Now we have the option to either contact stakeholders directly to do it in a much more effective synchronous manner to expedite things or plea a second time in a public forum for this CTA in the hope they read and take action on time.
Please stop trying to see issues in everything because the boy cried wolf effect is enormous and you’re hurting morale.
Bas
> Op 18 mei 2019, om 15:24 heeft Justin Mclean <ju...@classsoftware.com> het volgende geschreven:
>
> Hi,
>
>> I nagged our mentors privately to vote and mentioned that I would be
>> trying a concurrent vote.
>
> IMO that communication should be public, part of doing things at the ASF is being open and tranparent. Again IMO that decision would of been better done via consensus of the PPMC and not conducted in private.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Sheng Wu <wu...@gmail.com>.
Hi
Look like the topic changed, somehow? Why?
This should a discussion about the possibility and recommendation about **parallel vote**.
Let’s stay in that one, OK?
----------------
Back to the topic, as both IPMC and Zipkin mentor,
**parallel vote** is good to improve the slow progress about incubator project release.
Apache NetBeans project is not alone, I have been there, also I took/am taking part in several incubating projects.
Not just as mentor or ASF perspective, but as a community member, feature contributor, even designer.
I have heard many many feedback about the time of release too long.
**parallel vote** fits the project which already have big community and mentors are active in voting and discussion.
We(Incubator) need at least 3 +1 from IPMC, which could be mentors, and mostly from mentors, when they are active.
Even in parallel mode, the IPMC still get at least 72 hours to recheck the release.
The purpose of incubator, from my understanding, is guiding the project to build the community, be familiar with ASF, following ASF way and get better.
If **parallel vote** could help the project in that way, in this case, I want to say yes.
I know, if the project community is too young, and the mentors are not active, parallel vote may make too many traffics.
I would suggest to get the suggestions from project mentors, they should be know the project better than other IPMC.
Sheng Wu
Apache Skywalking, ShardingSphere, Zipkin
> 在 2019年5月18日,下午9:24,Justin Mclean <ju...@classsoftware.com> 写道:
>
> Hi,
>
>> I nagged our mentors privately to vote and mentioned that I would be
>> trying a concurrent vote.
>
> IMO that communication should be public, part of doing things at the ASF is being open and tranparent. Again IMO that decision would of been better done via consensus of the PPMC and not conducted in private.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I nagged our mentors privately to vote and mentioned that I would be
> trying a concurrent vote.
IMO that communication should be public, part of doing things at the ASF is being open and tranparent. Again IMO that decision would of been better done via consensus of the PPMC and not conducted in private.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Willem Jiang <wi...@gmail.com>.
Yes, we (mentors of Zipkin) were informed about the vote in private mail.
I think it should be fine to ping mentor privately about the release
vote, as we cannot always monitor the dev mailing list.
Otherwise, it will some time for us to response the release vote.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Sat, May 18, 2019 at 5:39 PM Adrian Cole <ad...@gmail.com> wrote:
>
> > Can you point me to where the PPMC has a discussion about this?
>
> I nagged our mentors privately to vote and mentioned that I would be
> trying a concurrent vote.
>
> Everyone in our PPMC is aware of the vote delay problem and this
> thread. We have had numerous discussions about this topic since
> incubation.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
> Can you point me to where the PPMC has a discussion about this?
I nagged our mentors privately to vote and mentioned that I would be
trying a concurrent vote.
Everyone in our PPMC is aware of the vote delay problem and this
thread. We have had numerous discussions about this topic since
incubation.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I informed our mentors.
Can you point me to where the PPMC has a discussion about this?
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
and I also said in the announcement that this was a concurrent vote.
On Sat, May 18, 2019, 7:55 AM Adrian Cole <ad...@gmail.com> wrote:
> I informed our mentors.
>
> On Sat, May 18, 2019, 2:03 AM Justin Mclean <ju...@classsoftware.com>
> wrote:
>
>> HI,
>>
>> Or better still if you want to try something new / not in line with
>> policy at least discuss it with the IPMC first and give them a heads up
>> that you are doing so.
>>
>> Thanks,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
I informed our mentors.
On Sat, May 18, 2019, 2:03 AM Justin Mclean <ju...@classsoftware.com>
wrote:
> HI,
>
> Or better still if you want to try something new / not in line with policy
> at least discuss it with the IPMC first and give them a heads up that you
> are doing so.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
Or better still if you want to try something new / not in line with policy at least discuss it with the IPMC first and give them a heads up that you are doing so.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Given your podling has made few releases and each one has had some issues I would suggest you did this too soon, but happy to see what other IPMC members have to say on this.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
Posted by Adrian Cole <ad...@apache.org>.
FWIW I tried this just recently and was requested to not do it again. Worth knowing https://lists.apache.org/thread.html/0571e9dd1b7711c588a38d8a664378ce7df31c72592edcbe8ab8a72b@%3Cgeneral.incubator.apache.org%3E
On 2019/04/02 09:30:10, Geertjan Wielenga <ge...@googlemail.com.INVALID> wrote:
> Maybe the PPMC and IPMC vote could run in parallel -- a key reason why we
> in Apache NetBeans are looking forward to graduation is that we'll not need
> to go through the loop of (1) PPMC approves, (2) IPMC rejects, (3) PPMC
> needs to put together a new release and vote on it again, (4) IPMC rejects
> again (finding something else they hadn't found before), etc. That's slowed
> the releases we have done in the incubator down significantly, typically by
> at least 2 weeks -- of course, as will be pointed out, Apache NetBeans is
> very large -- but, assuming Apache wants to be a welcome place for large
> projects too, something needs to be done here (though it won't be a problem
> for Apache NetBeans anymore since we plan to graduate before our next
> release). So, if the votes were to at least run in parallel, that would
> save time, and maybe as soon as there are 3 +1s from PPMC/IPMC members,
> that should be good to go, rather than waiting another 72 hours after that,
> in situations where those votes come in quickly.
>
> Gj
>
> On Tue, Apr 2, 2019 at 11:09 AM Julian Feinauer <
> j.feinauer@pragmaticminds.de> wrote:
>
> > Hi,
> >
> > I like Craigs suggestion and I'm aware of the problem with the ASF Policy
> > if we would skip the formal IPMC Vote.
> > On the other hand in PLC4X we had a discussion about a regular release
> > cycle to bring new features to the users as fast as possible and decided to
> > skip that for now, to keep the burden on the IPMC low (and we usually have
> > 3 IPMC / Mentor Votes as we have very active Mentors).
> > I agree with this decision of the PPMC but I see a problem with that, as
> > the IPMC Vote should be something to help podlings (aside from the
> > necessity by Policy) but not "negatively" impact them.
> >
> > Perhaps it helps to see the IPMC Votes more as a "take notice" in case
> > that there are already 3 +1 Votes. This means that the vote is open for
> > 72hrs formally, but IPMC members do not feel to have to go to action
> > (usually as PMC member one "should" participate in votes... although this
> > is practiced differently in the IPMC for good reasons) but CAN if they feel
> > like.
> > This would especially mean that podlings should be encouraged to formulate
> > their votes more explicit about whether there are already enough IPMC Votes
> > or not.
> >
> > Julian
> >
> >
> > Am 01.04.19, 23:51 schrieb "Justin Mclean" <ju...@classsoftware.com>:
> >
> > Hi,
> >
> > I'd also like to see those mentors / IPMC members vote with more than
> > just a +1 and provide a list of what they checked. If they could use
> > something like this all the better [1].
> >
> > I wouldn’t be for removing the second step of letting the IPMC look at
> > it, reasonably often serious issues are found in that step. By skilling
> > that we risk some podlings going all the way to propose graduation while
> > having releases that don’t follow ASF policy. This is a situation I’d like
> > to avoid.
> >
> > Thanks,
> > Justin
> >
> > 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Julian Feinauer <j....@pragmaticminds.de>.
I agree with the point from Myrle and Ross, I dislike the idea of parallel votes.
Especially in the early stages we had multiple RCs which failed in the PPMC Vote process.
I would not like to have them on the general@ list, as that adds a lot of noise.
Julian
Am 02.04.19, 16:41 schrieb "Ross Gardler" <rg...@outlook.com>:
Myrle makes a good point. As a mentor (is been a long time though) I tried to cast my vote after there were at least 3 views from the community. Once I saw the ppmc catching issues I was missing, or I was simply ratifying their view, it was time to graduate.
The IPMC should have nothing to do with it, other than as a backstop for absent mentors.
Interested IPMC members can join the community like everyone else. They are not some privileged group that gets special treatment.
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Myrle Krantz <my...@apache.org>
Sent: Tuesday, April 2, 2019 7:31:41 AM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
On Tue, Apr 2, 2019 at 2:09 PM Bertrand Delacretaz <
bdelacretaz@codeconsult.ch> wrote:
> Hi,
>
> On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
> > ...Maybe the PPMC and IPMC vote could run in parallel...
>
> I think the reason for having two votes is to give an opportunity for
> mentors to catch issues in the first one without bothering the IPMC.
>
The vote on the podling list is more (in my opinion) about giving the
members of the PPMC hands-on practice in catching issues before the safety
net of mentors/IPMC comes into play. This is one reason why some mentors
sometimes chose to wait a bit before voting on releases.
Best Regards,
Myrle
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ate Douma <at...@douma.nu>.
On 02/04/2019 16.53, Ate Douma wrote:
>
>
> On 02/04/2019 16.41, Ross Gardler wrote:
>> Myrle makes a good point. As a mentor (is been a long time though) I
>> tried to cast my vote after there were at least 3 views from the
>> community. Once I saw the ppmc catching issues I was missing, or I was
>> simply ratifying their view, it was time to graduate.
>>
>> The IPMC should have nothing to do with it, other than as a backstop
>> for absent mentors.
>>
>> Interested IPMC members can join the community like everyone else.
>> They are not some privileged group that gets special treatment.
>
> I agree and like this!
>
> Can we change the rules such that a PPMC release vote only needs to
> be notified to the IPMC (general@), and without further ado be accepted
> when at least +3 binding votes have been given on the podling dev list?
> That leaves room for other interested IPMC members to participate in the
> vote *there*, but won't depend on it.
> Only when not enough binding IPMC votes are collected during the podling
> release vote, it can either be re-started on general@, or a heads-up can
> be send there requesting explicit help from other IPMC members.
Furthermore, this makes the responsibilities of mentors more explicit,
as well as possible lack of time (MIA) of mentors.
Also, if mentors are not completely sure about complicated release
matters, they can choose to vote +0, with reasons, thereby indicating
the need for more IPMC eyes to review the release.
In case of huge/complex podlings like NetBeans that clearly was needed
and tremendously helpful.
>
>>
>> Get Outlook for Android<https://aka.ms/ghei36>
>>
>> ________________________________
>> From: Myrle Krantz <my...@apache.org>
>> Sent: Tuesday, April 2, 2019 7:31:41 AM
>> To: general@incubator.apache.org
>> Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior
>> to asking IPMC to vote
>>
>> On Tue, Apr 2, 2019 at 2:09 PM Bertrand Delacretaz <
>> bdelacretaz@codeconsult.ch> wrote:
>>
>>> Hi,
>>>
>>> On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
>>> <ge...@googlemail.com.invalid> wrote:
>>>> ...Maybe the PPMC and IPMC vote could run in parallel...
>>>
>>> I think the reason for having two votes is to give an opportunity for
>>> mentors to catch issues in the first one without bothering the IPMC.
>>>
>>
>> The vote on the podling list is more (in my opinion) about giving the
>> members of the PPMC hands-on practice in catching issues before the
>> safety
>> net of mentors/IPMC comes into play. This is one reason why some mentors
>> sometimes chose to wait a bit before voting on releases.
>>
>> Best Regards,
>> Myrle
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ate Douma <at...@douma.nu>.
On 02/04/2019 16.41, Ross Gardler wrote:
> Myrle makes a good point. As a mentor (is been a long time though) I tried to cast my vote after there were at least 3 views from the community. Once I saw the ppmc catching issues I was missing, or I was simply ratifying their view, it was time to graduate.
>
> The IPMC should have nothing to do with it, other than as a backstop for absent mentors.
>
> Interested IPMC members can join the community like everyone else. They are not some privileged group that gets special treatment.
I agree and like this!
Can we change the rules such that a PPMC release vote only needs to
be notified to the IPMC (general@), and without further ado be accepted
when at least +3 binding votes have been given on the podling dev list?
That leaves room for other interested IPMC members to participate in the
vote *there*, but won't depend on it.
Only when not enough binding IPMC votes are collected during the podling
release vote, it can either be re-started on general@, or a heads-up can
be send there requesting explicit help from other IPMC members.
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> ________________________________
> From: Myrle Krantz <my...@apache.org>
> Sent: Tuesday, April 2, 2019 7:31:41 AM
> To: general@incubator.apache.org
> Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
>
> On Tue, Apr 2, 2019 at 2:09 PM Bertrand Delacretaz <
> bdelacretaz@codeconsult.ch> wrote:
>
>> Hi,
>>
>> On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
>> <ge...@googlemail.com.invalid> wrote:
>>> ...Maybe the PPMC and IPMC vote could run in parallel...
>>
>> I think the reason for having two votes is to give an opportunity for
>> mentors to catch issues in the first one without bothering the IPMC.
>>
>
> The vote on the podling list is more (in my opinion) about giving the
> members of the PPMC hands-on practice in catching issues before the safety
> net of mentors/IPMC comes into play. This is one reason why some mentors
> sometimes chose to wait a bit before voting on releases.
>
> Best Regards,
> Myrle
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ross Gardler <rg...@outlook.com>.
Myrle makes a good point. As a mentor (is been a long time though) I tried to cast my vote after there were at least 3 views from the community. Once I saw the ppmc catching issues I was missing, or I was simply ratifying their view, it was time to graduate.
The IPMC should have nothing to do with it, other than as a backstop for absent mentors.
Interested IPMC members can join the community like everyone else. They are not some privileged group that gets special treatment.
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Myrle Krantz <my...@apache.org>
Sent: Tuesday, April 2, 2019 7:31:41 AM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
On Tue, Apr 2, 2019 at 2:09 PM Bertrand Delacretaz <
bdelacretaz@codeconsult.ch> wrote:
> Hi,
>
> On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
> > ...Maybe the PPMC and IPMC vote could run in parallel...
>
> I think the reason for having two votes is to give an opportunity for
> mentors to catch issues in the first one without bothering the IPMC.
>
The vote on the podling list is more (in my opinion) about giving the
members of the PPMC hands-on practice in catching issues before the safety
net of mentors/IPMC comes into play. This is one reason why some mentors
sometimes chose to wait a bit before voting on releases.
Best Regards,
Myrle
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Myrle Krantz <my...@apache.org>.
On Tue, Apr 2, 2019 at 2:09 PM Bertrand Delacretaz <
bdelacretaz@codeconsult.ch> wrote:
> Hi,
>
> On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
> > ...Maybe the PPMC and IPMC vote could run in parallel...
>
> I think the reason for having two votes is to give an opportunity for
> mentors to catch issues in the first one without bothering the IPMC.
>
The vote on the podling list is more (in my opinion) about giving the
members of the PPMC hands-on practice in catching issues before the safety
net of mentors/IPMC comes into play. This is one reason why some mentors
sometimes chose to wait a bit before voting on releases.
Best Regards,
Myrle
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ate Douma <at...@douma.nu>.
On 02/04/2019 13.58, Bertrand Delacretaz wrote:
> Hi,
>
> On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
>> ...Maybe the PPMC and IPMC vote could run in parallel...
>
> I think the reason for having two votes is to give an opportunity for
> mentors to catch issues in the first one without bothering the IPMC.
That, as well as the actual/target voting audience, including the PPMC
and the podling community, which more likely will also, and more so,
verify and validate the actual intended functionality (runtime) of
the release.
While the IPMC will be more/mostly focussed on the formal requirements
(license/notice files, dependencies, no binaries in source, etc.).
Running both votes in parallel definitely can be useful, but the
release manager then may want/need to take *both* vote results into
account in deciding the result (with +3 binding IPMC votes as a minimum
requirement).
>
> So maybe run parallel votes from the third or fourth release on, to
> keep the "noise filter" active initially.
Yes, or at least do the first release votes sequentially, and thereafter
opt for using parallel votes based on the advise from the mentors.
And it might still be recommended to do a sequential vote later on in
case of huge or major changes, for example after a big code donation
being incorporated.
Ate
>
> This is similar to having to report monthly for the first three
> months, then quarterly.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Hi,
On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
> ...Maybe the PPMC and IPMC vote could run in parallel...
I think the reason for having two votes is to give an opportunity for
mentors to catch issues in the first one without bothering the IPMC.
So maybe run parallel votes from the third or fourth release on, to
keep the "noise filter" active initially.
This is similar to having to report monthly for the first three
months, then quarterly.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
Parallel would solve our problem of delayed bookkeeping as well. good idea.
It is not so much about about the initial 72 hours, rather the pause
then another 72hrs that someone having to remember. Podlings have a
stateful experience during a release.. they have to know which are in
what stage. voting is more stateless. My goal is to have podlings and
folks who have stateful tasks to be able to complete them with no more
stages than necessary.
People will drive up quality to have less burdensome process. You'll
notice zipkin already automating things people have been emburdened by
for years [1] . If higher gates are needed for a faster process, I'm
sure we'd find a way to do that vs the alternative. No ones goal is to
do more red tape than necessary or take longer doing it I'm sure.
-A
[1] https://github.com/openzipkin-contrib/apache-release-verification
On Tue, Apr 2, 2019 at 4:30 PM Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
>
> Maybe the PPMC and IPMC vote could run in parallel -- a key reason why we
> in Apache NetBeans are looking forward to graduation is that we'll not need
> to go through the loop of (1) PPMC approves, (2) IPMC rejects, (3) PPMC
> needs to put together a new release and vote on it again, (4) IPMC rejects
> again (finding something else they hadn't found before), etc. That's slowed
> the releases we have done in the incubator down significantly, typically by
> at least 2 weeks -- of course, as will be pointed out, Apache NetBeans is
> very large -- but, assuming Apache wants to be a welcome place for large
> projects too, something needs to be done here (though it won't be a problem
> for Apache NetBeans anymore since we plan to graduate before our next
> release). So, if the votes were to at least run in parallel, that would
> save time, and maybe as soon as there are 3 +1s from PPMC/IPMC members,
> that should be good to go, rather than waiting another 72 hours after that,
> in situations where those votes come in quickly.
>
> Gj
>
> On Tue, Apr 2, 2019 at 11:09 AM Julian Feinauer <
> j.feinauer@pragmaticminds.de> wrote:
>
> > Hi,
> >
> > I like Craigs suggestion and I'm aware of the problem with the ASF Policy
> > if we would skip the formal IPMC Vote.
> > On the other hand in PLC4X we had a discussion about a regular release
> > cycle to bring new features to the users as fast as possible and decided to
> > skip that for now, to keep the burden on the IPMC low (and we usually have
> > 3 IPMC / Mentor Votes as we have very active Mentors).
> > I agree with this decision of the PPMC but I see a problem with that, as
> > the IPMC Vote should be something to help podlings (aside from the
> > necessity by Policy) but not "negatively" impact them.
> >
> > Perhaps it helps to see the IPMC Votes more as a "take notice" in case
> > that there are already 3 +1 Votes. This means that the vote is open for
> > 72hrs formally, but IPMC members do not feel to have to go to action
> > (usually as PMC member one "should" participate in votes... although this
> > is practiced differently in the IPMC for good reasons) but CAN if they feel
> > like.
> > This would especially mean that podlings should be encouraged to formulate
> > their votes more explicit about whether there are already enough IPMC Votes
> > or not.
> >
> > Julian
> >
> >
> > Am 01.04.19, 23:51 schrieb "Justin Mclean" <ju...@classsoftware.com>:
> >
> > Hi,
> >
> > I'd also like to see those mentors / IPMC members vote with more than
> > just a +1 and provide a list of what they checked. If they could use
> > something like this all the better [1].
> >
> > I wouldn’t be for removing the second step of letting the IPMC look at
> > it, reasonably often serious issues are found in that step. By skilling
> > that we risk some podlings going all the way to propose graduation while
> > having releases that don’t follow ASF policy. This is a situation I’d like
> > to avoid.
> >
> > Thanks,
> > Justin
> >
> > 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Maybe the PPMC and IPMC vote could run in parallel -- a key reason why we
in Apache NetBeans are looking forward to graduation is that we'll not need
to go through the loop of (1) PPMC approves, (2) IPMC rejects, (3) PPMC
needs to put together a new release and vote on it again, (4) IPMC rejects
again (finding something else they hadn't found before), etc. That's slowed
the releases we have done in the incubator down significantly, typically by
at least 2 weeks -- of course, as will be pointed out, Apache NetBeans is
very large -- but, assuming Apache wants to be a welcome place for large
projects too, something needs to be done here (though it won't be a problem
for Apache NetBeans anymore since we plan to graduate before our next
release). So, if the votes were to at least run in parallel, that would
save time, and maybe as soon as there are 3 +1s from PPMC/IPMC members,
that should be good to go, rather than waiting another 72 hours after that,
in situations where those votes come in quickly.
Gj
On Tue, Apr 2, 2019 at 11:09 AM Julian Feinauer <
j.feinauer@pragmaticminds.de> wrote:
> Hi,
>
> I like Craigs suggestion and I'm aware of the problem with the ASF Policy
> if we would skip the formal IPMC Vote.
> On the other hand in PLC4X we had a discussion about a regular release
> cycle to bring new features to the users as fast as possible and decided to
> skip that for now, to keep the burden on the IPMC low (and we usually have
> 3 IPMC / Mentor Votes as we have very active Mentors).
> I agree with this decision of the PPMC but I see a problem with that, as
> the IPMC Vote should be something to help podlings (aside from the
> necessity by Policy) but not "negatively" impact them.
>
> Perhaps it helps to see the IPMC Votes more as a "take notice" in case
> that there are already 3 +1 Votes. This means that the vote is open for
> 72hrs formally, but IPMC members do not feel to have to go to action
> (usually as PMC member one "should" participate in votes... although this
> is practiced differently in the IPMC for good reasons) but CAN if they feel
> like.
> This would especially mean that podlings should be encouraged to formulate
> their votes more explicit about whether there are already enough IPMC Votes
> or not.
>
> Julian
>
>
> Am 01.04.19, 23:51 schrieb "Justin Mclean" <ju...@classsoftware.com>:
>
> Hi,
>
> I'd also like to see those mentors / IPMC members vote with more than
> just a +1 and provide a list of what they checked. If they could use
> something like this all the better [1].
>
> I wouldn’t be for removing the second step of letting the IPMC look at
> it, reasonably often serious issues are found in that step. By skilling
> that we risk some podlings going all the way to propose graduation while
> having releases that don’t follow ASF policy. This is a situation I’d like
> to avoid.
>
> Thanks,
> Justin
>
> 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi,
I like Craigs suggestion and I'm aware of the problem with the ASF Policy if we would skip the formal IPMC Vote.
On the other hand in PLC4X we had a discussion about a regular release cycle to bring new features to the users as fast as possible and decided to skip that for now, to keep the burden on the IPMC low (and we usually have 3 IPMC / Mentor Votes as we have very active Mentors).
I agree with this decision of the PPMC but I see a problem with that, as the IPMC Vote should be something to help podlings (aside from the necessity by Policy) but not "negatively" impact them.
Perhaps it helps to see the IPMC Votes more as a "take notice" in case that there are already 3 +1 Votes. This means that the vote is open for 72hrs formally, but IPMC members do not feel to have to go to action (usually as PMC member one "should" participate in votes... although this is practiced differently in the IPMC for good reasons) but CAN if they feel like.
This would especially mean that podlings should be encouraged to formulate their votes more explicit about whether there are already enough IPMC Votes or not.
Julian
Am 01.04.19, 23:51 schrieb "Justin Mclean" <ju...@classsoftware.com>:
Hi,
I'd also like to see those mentors / IPMC members vote with more than just a +1 and provide a list of what they checked. If they could use something like this all the better [1].
I wouldn’t be for removing the second step of letting the IPMC look at it, reasonably often serious issues are found in that step. By skilling that we risk some podlings going all the way to propose graduation while having releases that don’t follow ASF policy. This is a situation I’d like to avoid.
Thanks,
Justin
1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Dave Fisher <da...@comcast.net>.
Hi -
> On Apr 1, 2019, at 2:51 PM, Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
> I'd also like to see those mentors / IPMC members vote with more than just a +1 and provide a list of what they checked. If they could use something like this all the better [1].
>
> I wouldn’t be for removing the second step of letting the IPMC look at it, reasonably often serious issues are found in that step. By skilling that we risk some podlings going all the way to propose graduation while having releases that don’t follow ASF policy. This is a situation I’d like to avoid.
If the podling has three engaged Mentors that do VOTE and move the podling forward then I would suggest following Myrle’s plan and the podling releases and then sends a [REVIEW] or [DISCUSS].
I also suggest that the are the mentor’s helpful include an are your mentor’s voting?
I know from my own experience that knowing that there will be a round of voting on general@ makes it easy for me to not hurry to VOTE on dev@.
Regards,
Dave
>
> Thanks,
> Justin
>
> 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi,
I like Craigs suggestion and I'm aware of the problem with the ASF Policy if we would skip the formal IPMC Vote.
On the other hand in PLC4X we had a discussion about a regular release cycle to bring new features to the users as fast as possible and decided to skip that for now, to keep the burden on the IPMC low (and we usually have 3 IPMC / Mentor Votes as we have very active Mentors).
I agree with this decision of the PPMC but I see a problem with that, as the IPMC Vote should be something to help podlings (aside from the necessity by Policy) but not "negatively" impact them.
Perhaps it helps to see the IPMC Votes more as a "take notice" in case that there are already 3 +1 Votes. This means that the vote is open for 72hrs formally, but IPMC members do not feel to have to go to action (usually as PMC member one "should" participate in votes... although this is practiced differently in the IPMC for good reasons) but CAN if they feel like.
This would especially mean that podlings should be encouraged to formulate their votes more explicit about whether there are already enough IPMC Votes or not.
Julian
Am 01.04.19, 23:51 schrieb "Justin Mclean" <ju...@classsoftware.com>:
Hi,
I'd also like to see those mentors / IPMC members vote with more than just a +1 and provide a list of what they checked. If they could use something like this all the better [1].
I wouldn’t be for removing the second step of letting the IPMC look at it, reasonably often serious issues are found in that step. By skilling that we risk some podlings going all the way to propose graduation while having releases that don’t follow ASF policy. This is a situation I’d like to avoid.
Thanks,
Justin
1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
I'd also like to see those mentors / IPMC members vote with more than just a +1 and provide a list of what they checked. If they could use something like this all the better [1].
I wouldn’t be for removing the second step of letting the IPMC look at it, reasonably often serious issues are found in that step. By skilling that we risk some podlings going all the way to propose graduation while having releases that don’t follow ASF policy. This is a situation I’d like to avoid.
Thanks,
Justin
1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Hi,
On Mon, Apr 1, 2019 at 5:30 AM Craig Russell <ap...@gmail.com> wrote:
>
> ...This is a proposal to recommend that all Mentors SHOULD vote on podling releases
> prior to sending the release for a vote to the IPMC....
There's already something about this in the (work in progress)
http://incubator.apache.org/cookbook/ under "podling releases":
> If three mentors have voted this means the "three +1 votes" requirement is already fulfilled
> when that second vote starts, which can speed up things
If you think this can be improved, pull requests, comments here or at
https://issues.apache.org/jira/browse/INCUBATOR-234 are welcome.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ross Gardler <ro...@gardler.me>.
Sure, policy is "Release votes SHOULD remain open for at least 72 hours."
The reasons for the SHOULD have been outlined already and should be well known to anyone who is in a podling since it's core to everything we do. I would have hoped champions would have explained this before even making the proposal. Not that it does any harm to repeat it.
Same goes for properly documenting what your +1 means. In the ASF +1 does not mean YES it means yes AND I have done what is necessary (in the case of indicating appropriate due diligence) or yes AND I will help make it happen (in the case of approving an action plan). Again, no harm in repeating this often.
It might be useful to give an example of where there is no need for a release vote to go 72 hours. A well run project will seek to have their code in a releasable state at all times. That means reviewing for IP, test coverage, backward compatibility breaks etc. on every commit. In the case of a minor point release or a bug fix release such projects MAY choose to release when 3 +1s are received. After all, if an issue is discovered on the 73rd hour a fix can be committed and a new release voted started immediately without creating additional work for anyone.
Ross
________________________________________
From: Justin Mclean <ju...@gmail.com>
Sent: Monday, April 1, 2019 3:42 PM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
Hi,
When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
> intending to rewrite foundation policy.
>
Sure I thought so as well, but other newer people here might not of been
aware of it.
Thanks,
Justin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
TL;DR; I suppose is that in the case of 3 mentor/IPMC already +1 a release
we can switch to a "review after commit" style notification so that folks
eager to double check can, but not to burden the project or IPMC with a
secondary step.
This not only reduces bookkeeping but encourages each podling to engage
mentors, helping with the original intent of this thread.
Anything noted as blocker review after commit would be addressed.
In the rare case that IPMC members acting in a podling are doing a bad job,
that could be addressed as a learning exercise as presumably they would
also be doing a bad job at the later vote too.
On Tue, Apr 2, 2019, 9:42 AM Adrian Cole <ad...@gmail.com> wrote:
> one part that may not be obvious is the bookkeeping overhead on projects
> with many repositories and also the load on the IPMC.
>
> For example in zipkin, we are migrating several repositories. You can
> imagine a surge of release verification votes which if people here want to
> take the burden of responding to, surely can. Noting that there are already
> several IPMC involved it might for some members feel less priority and they
> may choose to not vote at all (such as our last release).
>
> Probably secondary to folks here is the burden on the podling to track the
> incomplete releases. It is less about rush more about excess tracking. It
> is possible that a project can achieve a "good driver status" to reduce the
> burden of having to create a wait condition especially if it is not the
> case people do anything during it.
>
> my 2p
>
> On Tue, Apr 2, 2019, 5:59 AM Dave Fisher <da...@comcast.net> wrote:
>
>>
>>
>> > On Apr 1, 2019, at 3:42 PM, Justin Mclean <ju...@gmail.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
>> >> intending to rewrite foundation policy.
>> >>
>> >
>> > Sure I thought so as well, but other newer people here might not of been
>> > aware of it.
>>
>> The only exception to the 72 hour rule that I’ve heard about is a
>> critical security fix needs to be made in which case I would hope the
>> reason for the hurry would be explained on private lists.
>>
>> I would not put words into Ross’s mouth. He may in fact mean that he
>> would go quickly when there are three +1 votes and reasons other than
>> security.
>>
>> Regards,
>> Dave
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
one part that may not be obvious is the bookkeeping overhead on projects
with many repositories and also the load on the IPMC.
For example in zipkin, we are migrating several repositories. You can
imagine a surge of release verification votes which if people here want to
take the burden of responding to, surely can. Noting that there are already
several IPMC involved it might for some members feel less priority and they
may choose to not vote at all (such as our last release).
Probably secondary to folks here is the burden on the podling to track the
incomplete releases. It is less about rush more about excess tracking. It
is possible that a project can achieve a "good driver status" to reduce the
burden of having to create a wait condition especially if it is not the
case people do anything during it.
my 2p
On Tue, Apr 2, 2019, 5:59 AM Dave Fisher <da...@comcast.net> wrote:
>
>
> > On Apr 1, 2019, at 3:42 PM, Justin Mclean <ju...@gmail.com>
> wrote:
> >
> > Hi,
> >
> > When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
> >> intending to rewrite foundation policy.
> >>
> >
> > Sure I thought so as well, but other newer people here might not of been
> > aware of it.
>
> The only exception to the 72 hour rule that I’ve heard about is a critical
> security fix needs to be made in which case I would hope the reason for the
> hurry would be explained on private lists.
>
> I would not put words into Ross’s mouth. He may in fact mean that he would
> go quickly when there are three +1 votes and reasons other than security.
>
> Regards,
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Dave Fisher <da...@comcast.net>.
> On Apr 1, 2019, at 3:42 PM, Justin Mclean <ju...@gmail.com> wrote:
>
> Hi,
>
> When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
>> intending to rewrite foundation policy.
>>
>
> Sure I thought so as well, but other newer people here might not of been
> aware of it.
The only exception to the 72 hour rule that I’ve heard about is a critical security fix needs to be made in which case I would hope the reason for the hurry would be explained on private lists.
I would not put words into Ross’s mouth. He may in fact mean that he would go quickly when there are three +1 votes and reasons other than security.
Regards,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@gmail.com>.
Hi,
When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
> intending to rewrite foundation policy.
>
Sure I thought so as well, but other newer people here might not of been
aware of it.
Thanks,
Justin
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Julian Hyde <jh...@apache.org>.
Per my reading http://www.apache.org/legal/release-policy.html#release-approval <http://www.apache.org/legal/release-policy.html#release-approval> it’s not OK to stop when you reach 3 +1 votes. Because it’s not 3 +1s absolute, it’s 3 more +1s than -1s. So, you have to have a fixed, reasonable timeframe for the vote to give those -1s time to accrue.
Release policy says the timeframe SHOULD be 72 hours. I can think of scenarios where it could be less, but you still have to give PMC members adequate notice.
When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not intending to rewrite foundation policy.
Also note in that same section:
> Before casting +1 binding votes, individuals are REQUIRED to download
> all signed source code packages onto their own hardware, verify that they
> meet all requirements of ASF policy on releases as described below,
> validate all cryptographic signatures, compile as provided, and test the
> result on their own platform.
This clearly establishes the minimum required of mentors voting for a podling release.
Lastly, I absolutely agree with the question in the subject line. Yes, Mentors SHOULD vote on podling releases prior to asking IPMC to vote.
As mentors are busy, and are not 100% focused on the podling, the podling should give them a little nudge and a little leeway. Case in point: Druid 0.14 started a vote at 4.08pm on Friday. It is now 3.08pm on Monday, i.e. we’re at 71 hours. I voted but the other 2 mentors (whom I would describe as “engaged”) have not yet. I just emailed them to ask them to vote. If they do not vote in the next hour, the release manager should keep the vote open for a while to give them chance to vote.
Julian
> On Apr 1, 2019, at 2:59 PM, Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
>> 72 hours is a guide. As long as your project community is agreeable you can say "72hrs or 3 +1”.
>
> 72 hours is a guide, but recommended, as it gives a chance for all PPMC members to have a look at the release. They may be in different timezone or have day jobs or other things going on, we are all volunteers here and not all of us work full time on a project. If that 72 hours was constantly reduced it would exclude certain groups of people looking at the release and I don’t think we want to do that. For instance I don’t think it would be OK if those 3 +1’s came in an hour of announcing the release candidate.
>
> Thanks,
> Justin
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> 72 hours is a guide. As long as your project community is agreeable you can say "72hrs or 3 +1”.
72 hours is a guide, but recommended, as it gives a chance for all PPMC members to have a look at the release. They may be in different timezone or have day jobs or other things going on, we are all volunteers here and not all of us work full time on a project. If that 72 hours was constantly reduced it would exclude certain groups of people looking at the release and I don’t think we want to do that. For instance I don’t think it would be OK if those 3 +1’s came in an hour of announcing the release candidate.
Thanks,
Justin
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ross Gardler <rg...@outlook.com>.
72 hours is a guide. As long as your project community is agreeable you can say "72hrs or 3 +1".
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Adrian Cole <ad...@gmail.com>
Sent: Sunday, March 31, 2019 9:26:08 PM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
I have a related question. In Zipkin (incubating) last release of one of
our projects, we had 3 IPMC +1 votes prior to the formal verification vote.
Then we basically just waited 72hrs anyway with no additional votes but it
didn't matter as we had what we needed (another came later but still) [1]
If a project already has 3 IPMC members active verifying and voting.. it
might feel a bit tedious to delay a release an additional 3+ days
especially if there is no additional feedback.
Not sure the answer here, but I hope the situation is relevant to the
thread. For example, should same rules apply when there are no additional
IPMC votes needed from what is carried over from the podling vote?
-A
[1]
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F6e26ccaecba70a5cde1f808d82499701562f370441067b96ca65f09a%40%253Cgeneral.incubator.apache.org%253E&data=02%7C01%7C%7Cf3f98ab49c294fdee58408d6b65a22eb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636896895573897795&sdata=oQg4R6ms2IRkfoGdVAf54vUrhXLaq9DIbmk%2F4SzwTvE%3D&reserved=0
On Mon, Apr 1, 2019, 11:15 AM Ross Gardler <rg...@outlook.com> wrote:
> Just like so many things, this is how it used to be. In fact, back in the
> day the only time the IPMC was asked to vote was when there were not enough
> mentor votes.
>
> If you look at all the podlinga I've mentored I have only ever asked for
> an IPMC vote on two occasions (that I recall). One because I had absent
> mentors (the project never graduated due to lack of success as a community)
> and one because it was a very large and complex code base and we asked for
> extra eyes on the first release.
>
> Every other time the community worked with mentors. Once we had the votes
> we notified the IPMC that the vote had passed and moved on.
>
> Requiring an IPMC vote is akin to the board voting on all TLP releases. It
> should be stopped. The IPMC are facilitators not gate keepers.
>
> Individual IPMC members can join the podling communities if they wish to
> participate. Why are podlings and mentors answering to the IPMC by default?
>
> I know the standard answer is because mentors sometimes get too busy.
> Sure. If it happens every release is a problem and having to ask for an
> IPMC vote highlights the problem.
>
> I realize this proposal does not go this far, I'm +0 for the proposal as a
> step in the right direction, but it doesn't go far enough in my opinion.
>
> Ross
>
> Get Outlook for Android<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7C%7Cf3f98ab49c294fdee58408d6b65a22eb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636896895573897795&sdata=pXkL0wr7fNysnARTzfPwP9pLFRmeJdpIQxFo8Y5Vyuo%3D&reserved=0>
>
> ________________________________
> From: Craig Russell <ap...@gmail.com>
> Sent: Sunday, March 31, 2019 8:30:35 PM
> To: Incubator
> Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
> IPMC to vote
>
> This is a proposal to recommend that all Mentors SHOULD vote on podling
> releases prior to sending the release for a vote to the IPMC.
>
> This is not a MUST, since there are many good reasons why a mentor might
> be unable to perform the checks needed to vote. We are volunteers after all.
>
> But if this proposal is adopted, it will minimize the occurrences of a
> podling desperately asking for someone, anyone, on the IPMC to please vote.
>
> It should also minimize the number of podling releases that are shot down
> in the full IPMC vote because of something that a Mentor is likely to catch.
>
> Thanks for your consideration,
>
> Craig
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Adrian Cole <ad...@gmail.com>.
I have a related question. In Zipkin (incubating) last release of one of
our projects, we had 3 IPMC +1 votes prior to the formal verification vote.
Then we basically just waited 72hrs anyway with no additional votes but it
didn't matter as we had what we needed (another came later but still) [1]
If a project already has 3 IPMC members active verifying and voting.. it
might feel a bit tedious to delay a release an additional 3+ days
especially if there is no additional feedback.
Not sure the answer here, but I hope the situation is relevant to the
thread. For example, should same rules apply when there are no additional
IPMC votes needed from what is carried over from the podling vote?
-A
[1]
https://lists.apache.org/thread.html/6e26ccaecba70a5cde1f808d82499701562f370441067b96ca65f09a@%3Cgeneral.incubator.apache.org%3E
On Mon, Apr 1, 2019, 11:15 AM Ross Gardler <rg...@outlook.com> wrote:
> Just like so many things, this is how it used to be. In fact, back in the
> day the only time the IPMC was asked to vote was when there were not enough
> mentor votes.
>
> If you look at all the podlinga I've mentored I have only ever asked for
> an IPMC vote on two occasions (that I recall). One because I had absent
> mentors (the project never graduated due to lack of success as a community)
> and one because it was a very large and complex code base and we asked for
> extra eyes on the first release.
>
> Every other time the community worked with mentors. Once we had the votes
> we notified the IPMC that the vote had passed and moved on.
>
> Requiring an IPMC vote is akin to the board voting on all TLP releases. It
> should be stopped. The IPMC are facilitators not gate keepers.
>
> Individual IPMC members can join the podling communities if they wish to
> participate. Why are podlings and mentors answering to the IPMC by default?
>
> I know the standard answer is because mentors sometimes get too busy.
> Sure. If it happens every release is a problem and having to ask for an
> IPMC vote highlights the problem.
>
> I realize this proposal does not go this far, I'm +0 for the proposal as a
> step in the right direction, but it doesn't go far enough in my opinion.
>
> Ross
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> ________________________________
> From: Craig Russell <ap...@gmail.com>
> Sent: Sunday, March 31, 2019 8:30:35 PM
> To: Incubator
> Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
> IPMC to vote
>
> This is a proposal to recommend that all Mentors SHOULD vote on podling
> releases prior to sending the release for a vote to the IPMC.
>
> This is not a MUST, since there are many good reasons why a mentor might
> be unable to perform the checks needed to vote. We are volunteers after all.
>
> But if this proposal is adopted, it will minimize the occurrences of a
> podling desperately asking for someone, anyone, on the IPMC to please vote.
>
> It should also minimize the number of podling releases that are shot down
> in the full IPMC vote because of something that a Mentor is likely to catch.
>
> Thanks for your consideration,
>
> Craig
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to askingIPMC to vote
Posted by 吴晟 Sheng Wu <wu...@foxmail.com>.
Have enough mentor votes in dev vote, and carry them to incubator vote, really could make the IPMC vote more flexible.
IPMC member could help on recheck from different view, which sometimes is necessary. Fresh eyes are good to the community and assist the project speed up to graduate, in my perspective. Even one or two IPMC vote -1, but the project mentors think still good enough to release, then the release wouldn't be blocked.
From my experiences, in SkyWalking as very new in ASF, in ShardingSphere as a member of PPMC goes through incubator journey again,
and in Zipkin as a project mentor, all these project PPMC team explicitly hope that, they could have this kind of help from mentors.
I am +1 for Craig's suggestion, and hope the mentors could have time to take part in the release checks.
------------------
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108
------------------ Original ------------------
From: "Ross Gardler"<rg...@outlook.com>;
Date: Mon, Apr 1, 2019 12:14 PM
To: "general@incubator.apache.org"<ge...@incubator.apache.org>;
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to askingIPMC to vote
Just like so many things, this is how it used to be. In fact, back in the day the only time the IPMC was asked to vote was when there were not enough mentor votes.
If you look at all the podlinga I've mentored I have only ever asked for an IPMC vote on two occasions (that I recall). One because I had absent mentors (the project never graduated due to lack of success as a community) and one because it was a very large and complex code base and we asked for extra eyes on the first release.
Every other time the community worked with mentors. Once we had the votes we notified the IPMC that the vote had passed and moved on.
Requiring an IPMC vote is akin to the board voting on all TLP releases. It should be stopped. The IPMC are facilitators not gate keepers.
Individual IPMC members can join the podling communities if they wish to participate. Why are podlings and mentors answering to the IPMC by default?
I know the standard answer is because mentors sometimes get too busy. Sure. If it happens every release is a problem and having to ask for an IPMC vote highlights the problem.
I realize this proposal does not go this far, I'm +0 for the proposal as a step in the right direction, but it doesn't go far enough in my opinion.
Ross
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Craig Russell <ap...@gmail.com>
Sent: Sunday, March 31, 2019 8:30:35 PM
To: Incubator
Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
This is a proposal to recommend that all Mentors SHOULD vote on podling releases prior to sending the release for a vote to the IPMC.
This is not a MUST, since there are many good reasons why a mentor might be unable to perform the checks needed to vote. We are volunteers after all.
But if this proposal is adopted, it will minimize the occurrences of a podling desperately asking for someone, anyone, on the IPMC to please vote.
It should also minimize the number of podling releases that are shot down in the full IPMC vote because of something that a Mentor is likely to catch.
Thanks for your consideration,
Craig
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by sebb <se...@gmail.com>.
On Mon, 1 Apr 2019 at 05:15, Ross Gardler <rg...@outlook.com> wrote:
>
> Just like so many things, this is how it used to be. In fact, back in the day the only time the IPMC was asked to vote was when there were not enough mentor votes.
>
> If you look at all the podlinga I've mentored I have only ever asked for an IPMC vote on two occasions (that I recall). One because I had absent mentors (the project never graduated due to lack of success as a community) and one because it was a very large and complex code base and we asked for extra eyes on the first release.
>
> Every other time the community worked with mentors. Once we had the votes we notified the IPMC that the vote had passed and moved on.
>
> Requiring an IPMC vote is akin to the board voting on all TLP releases. It should be stopped. The IPMC are facilitators not gate keepers.
I'm not sure that is a correct analogy.
IMO the Incubator is the PMC for all its podlings.
I think it's more akin to Commons where each component tends to be
worked on by a few developers, but the whole PMC participates in
votes.
> Individual IPMC members can join the podling communities if they wish to participate. Why are podlings and mentors answering to the IPMC by default?
>
> I know the standard answer is because mentors sometimes get too busy. Sure. If it happens every release is a problem and having to ask for an IPMC vote highlights the problem.
>
> I realize this proposal does not go this far, I'm +0 for the proposal as a step in the right direction, but it doesn't go far enough in my opinion.
>
> Ross
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> ________________________________
> From: Craig Russell <ap...@gmail.com>
> Sent: Sunday, March 31, 2019 8:30:35 PM
> To: Incubator
> Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
>
> This is a proposal to recommend that all Mentors SHOULD vote on podling releases prior to sending the release for a vote to the IPMC.
>
> This is not a MUST, since there are many good reasons why a mentor might be unable to perform the checks needed to vote. We are volunteers after all.
>
> But if this proposal is adopted, it will minimize the occurrences of a podling desperately asking for someone, anyone, on the IPMC to please vote.
>
> It should also minimize the number of podling releases that are shot down in the full IPMC vote because of something that a Mentor is likely to catch.
>
> Thanks for your consideration,
>
> Craig
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
IPMC to vote
Posted by Ross Gardler <rg...@outlook.com>.
Just like so many things, this is how it used to be. In fact, back in the day the only time the IPMC was asked to vote was when there were not enough mentor votes.
If you look at all the podlinga I've mentored I have only ever asked for an IPMC vote on two occasions (that I recall). One because I had absent mentors (the project never graduated due to lack of success as a community) and one because it was a very large and complex code base and we asked for extra eyes on the first release.
Every other time the community worked with mentors. Once we had the votes we notified the IPMC that the vote had passed and moved on.
Requiring an IPMC vote is akin to the board voting on all TLP releases. It should be stopped. The IPMC are facilitators not gate keepers.
Individual IPMC members can join the podling communities if they wish to participate. Why are podlings and mentors answering to the IPMC by default?
I know the standard answer is because mentors sometimes get too busy. Sure. If it happens every release is a problem and having to ask for an IPMC vote highlights the problem.
I realize this proposal does not go this far, I'm +0 for the proposal as a step in the right direction, but it doesn't go far enough in my opinion.
Ross
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Craig Russell <ap...@gmail.com>
Sent: Sunday, March 31, 2019 8:30:35 PM
To: Incubator
Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote
This is a proposal to recommend that all Mentors SHOULD vote on podling releases prior to sending the release for a vote to the IPMC.
This is not a MUST, since there are many good reasons why a mentor might be unable to perform the checks needed to vote. We are volunteers after all.
But if this proposal is adopted, it will minimize the occurrences of a podling desperately asking for someone, anyone, on the IPMC to please vote.
It should also minimize the number of podling releases that are shot down in the full IPMC vote because of something that a Mentor is likely to catch.
Thanks for your consideration,
Craig
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org