Re: Podling binding votes
Hi, On Fri, Jul 25, 2014 at 12:57 AM, Justin Mclean jus...@classsoftware.com wrote: ...Whose votes are binding for releases on the podlings dev list?... Technically as Ross says, only votes from Incubator PMC members are binding as far as the ASF is concerned. What matters is getting 3 such binding votes, so that the release is an act of the Incubator PMC. IMO the rest is more social/educational. For the initial vote on the podling dev list I don't care too much whether voters are PPMC members or not, what's important is for the podling to establish consensus on asking the Incubator PMC to approve the release. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
The PPMC is not, and never has been, a formally recognized part of our structure. But as I said that's a technicality in this context, the project (PPMC) are the people who really matter from the projects perspective, even though their votes are not binding. The thread seems to be in agreement in response to Justin's specific question. On 25 Jul 2014 01:20, John D. Ament john.d.am...@gmail.com wrote: Ross, The incubator website would be inclined to disagree, and seems to acknowledge there is formally a PPMC at [1]. Justin, I think formally, if you review [2] (you may also want to scroll down, and review later parts of this page on voting), you'll see that the PPMC votes really don't count for anything other than merit. The IPMC vote is what really counts. If you follow that page verbatim, the votes by the IPMC are the only ones that count. If you follow the alternative voting method, found at [3], you'll see that votes via PPMC are acceptable if and only if the IPMC has agreed to such. [1]: http://incubator.apache.org/guides/ppmc.html [2]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote [3]: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler rgard...@opendirective.com wrote: There is no formal PPMC. When a podling is created all initial committers are equal. I guess some podlings might create the concept of a separate PPMC during incubation. I've never advised that in my own podlings (probably because I'm a believer in an absolute minimum barrier to entry). I guess it's up to individual projects and mentors just as our top level projects can decide if the PMC is the whole set or a subset of the committers On 25 Jul 2014 00:33, Justin Mclean jus...@classsoftware.com wrote: Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
On Fri, Jul 25, 2014 at 9:52 AM, Ross Gardler rgard...@opendirective.com wrote: ...the project (PPMC) are the people who really matter from the projects perspective, even though their votes are not binding Yeah, a good summary might be that the podling PPMC (+community) establishes consensus about releasing, and the Incubator PMC members make the release an act of the ASF. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
This is conflicting from what the site said about governance of podling. PPMC is a part of podling and responsible to manage the podling on behalf of IPMC. I suppose you meant that their votes do not bind but saying it was never part of the structure is misleading or we need to update the ASF website about incubator roles page. On Friday, July 25, 2014, Ross Gardler rgard...@opendirective.com wrote: The PPMC is not, and never has been, a formally recognized part of our structure. But as I said that's a technicality in this context, the project (PPMC) are the people who really matter from the projects perspective, even though their votes are not binding. The thread seems to be in agreement in response to Justin's specific question. On 25 Jul 2014 01:20, John D. Ament john.d.am...@gmail.com javascript:; wrote: Ross, The incubator website would be inclined to disagree, and seems to acknowledge there is formally a PPMC at [1]. Justin, I think formally, if you review [2] (you may also want to scroll down, and review later parts of this page on voting), you'll see that the PPMC votes really don't count for anything other than merit. The IPMC vote is what really counts. If you follow that page verbatim, the votes by the IPMC are the only ones that count. If you follow the alternative voting method, found at [3], you'll see that votes via PPMC are acceptable if and only if the IPMC has agreed to such. [1]: http://incubator.apache.org/guides/ppmc.html [2]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote [3]: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler rgard...@opendirective.com javascript:; wrote: There is no formal PPMC. When a podling is created all initial committers are equal. I guess some podlings might create the concept of a separate PPMC during incubation. I've never advised that in my own podlings (probably because I'm a believer in an absolute minimum barrier to entry). I guess it's up to individual projects and mentors just as our top level projects can decide if the PMC is the whole set or a subset of the committers On 25 Jul 2014 00:33, Justin Mclean jus...@classsoftware.com javascript:; wrote: Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:;
Re: Podling binding votes
On Fri, Jul 25, 2014 at 12:33 PM, Henry Saputra henry.sapu...@gmail.com wrote: This is conflicting from what the site said about governance of podling. PPMC is a part of podling and responsible to manage the podling on behalf of IPMC. I suppose you meant that their votes do not bind but saying it was never part of the structure is misleading or we need to update the ASF website about incubator roles page. The conflicting bit is how you two are resolving the pronoun our in Ross' statement below the PPMC is not a formal part of the ASF's formal structure the PPMC is a formal part of the IPMC's internal organization. --tim On Friday, July 25, 2014, Ross Gardler rgard...@opendirective.com wrote: The PPMC is not, and never has been, a formally recognized part of our structure. But as I said that's a technicality in this context, the project (PPMC) are the people who really matter from the projects perspective, even though their votes are not binding. The thread seems to be in agreement in response to Justin's specific question. On 25 Jul 2014 01:20, John D. Ament john.d.am...@gmail.com javascript:; wrote: Ross, The incubator website would be inclined to disagree, and seems to acknowledge there is formally a PPMC at [1]. Justin, I think formally, if you review [2] (you may also want to scroll down, and review later parts of this page on voting), you'll see that the PPMC votes really don't count for anything other than merit. The IPMC vote is what really counts. If you follow that page verbatim, the votes by the IPMC are the only ones that count. If you follow the alternative voting method, found at [3], you'll see that votes via PPMC are acceptable if and only if the IPMC has agreed to such. [1]: http://incubator.apache.org/guides/ppmc.html [2]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote [3]: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler rgard...@opendirective.com javascript:; wrote: There is no formal PPMC. When a podling is created all initial committers are equal. I guess some podlings might create the concept of a separate PPMC during incubation. I've never advised that in my own podlings (probably because I'm a believer in an absolute minimum barrier to entry). I guess it's up to individual projects and mentors just as our top level projects can decide if the PMC is the whole set or a subset of the committers On 25 Jul 2014 00:33, Justin Mclean jus...@classsoftware.com javascript:; wrote: Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
Touché :) On Friday, July 25, 2014, Tim Williams william...@gmail.com wrote: On Fri, Jul 25, 2014 at 12:33 PM, Henry Saputra henry.sapu...@gmail.com javascript:; wrote: This is conflicting from what the site said about governance of podling. PPMC is a part of podling and responsible to manage the podling on behalf of IPMC. I suppose you meant that their votes do not bind but saying it was never part of the structure is misleading or we need to update the ASF website about incubator roles page. The conflicting bit is how you two are resolving the pronoun our in Ross' statement below the PPMC is not a formal part of the ASF's formal structure the PPMC is a formal part of the IPMC's internal organization. --tim On Friday, July 25, 2014, Ross Gardler rgard...@opendirective.com javascript:; wrote: The PPMC is not, and never has been, a formally recognized part of our structure. But as I said that's a technicality in this context, the project (PPMC) are the people who really matter from the projects perspective, even though their votes are not binding. The thread seems to be in agreement in response to Justin's specific question. On 25 Jul 2014 01:20, John D. Ament john.d.am...@gmail.com javascript:; javascript:; wrote: Ross, The incubator website would be inclined to disagree, and seems to acknowledge there is formally a PPMC at [1]. Justin, I think formally, if you review [2] (you may also want to scroll down, and review later parts of this page on voting), you'll see that the PPMC votes really don't count for anything other than merit. The IPMC vote is what really counts. If you follow that page verbatim, the votes by the IPMC are the only ones that count. If you follow the alternative voting method, found at [3], you'll see that votes via PPMC are acceptable if and only if the IPMC has agreed to such. [1]: http://incubator.apache.org/guides/ppmc.html [2]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote [3]: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler rgard...@opendirective.com javascript:; javascript:; wrote: There is no formal PPMC. When a podling is created all initial committers are equal. I guess some podlings might create the concept of a separate PPMC during incubation. I've never advised that in my own podlings (probably because I'm a believer in an absolute minimum barrier to entry). I guess it's up to individual projects and mentors just as our top level projects can decide if the PMC is the whole set or a subset of the committers On 25 Jul 2014 00:33, Justin Mclean jus...@classsoftware.com javascript:; javascript:; wrote: Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; javascript:; - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:;
Podling binding votes
Hi, Anyone clarify this as it's not mentioned at [1]. Whose votes are binding for releases on the podlings dev list? Obviously mentors and PPMC members, but are IPMC members votes binding? I would assume so but don't see it stated anywhere. Would Apache members votes be binding? Assuming IPMC votes are binding what happen if a podling release dev list vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator or not? Thanks, Justin 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. I'm sure that some folks might claim the more correct process is to have a second vote, but as long as the 3 IPMC votes are formally and publicly recorded in the dev list vote then I believe that is all we need. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. Note I'm not suggesting that a PPMC vote is unimportant. In fact it is more important than IPMC votes at the project level, it's just the way we are structured means PPMC votes are not binding according to our bylaws (at least that's how I understand it). Sent from Surface From: Justin Mclean Sent: Thursday, July 24, 2014 3:57 PM To: general@incubator.apache.org Hi, Anyone clarify this as it's not mentioned at [1]. Whose votes are binding for releases on the podlings dev list? Obviously mentors and PPMC members, but are IPMC members votes binding? I would assume so but don't see it stated anywhere. Would Apache members votes be binding? Assuming IPMC votes are binding what happen if a podling release dev list vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator or not? Thanks, Justin 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
There is no formal PPMC. When a podling is created all initial committers are equal. I guess some podlings might create the concept of a separate PPMC during incubation. I've never advised that in my own podlings (probably because I'm a believer in an absolute minimum barrier to entry). I guess it's up to individual projects and mentors just as our top level projects can decide if the PMC is the whole set or a subset of the committers On 25 Jul 2014 00:33, Justin Mclean jus...@classsoftware.com wrote: Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
Ross, The incubator website would be inclined to disagree, and seems to acknowledge there is formally a PPMC at [1]. Justin, I think formally, if you review [2] (you may also want to scroll down, and review later parts of this page on voting), you'll see that the PPMC votes really don't count for anything other than merit. The IPMC vote is what really counts. If you follow that page verbatim, the votes by the IPMC are the only ones that count. If you follow the alternative voting method, found at [3], you'll see that votes via PPMC are acceptable if and only if the IPMC has agreed to such. [1]: http://incubator.apache.org/guides/ppmc.html [2]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote [3]: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler rgard...@opendirective.com wrote: There is no formal PPMC. When a podling is created all initial committers are equal. I guess some podlings might create the concept of a separate PPMC during incubation. I've never advised that in my own podlings (probably because I'm a believer in an absolute minimum barrier to entry). I guess it's up to individual projects and mentors just as our top level projects can decide if the PMC is the whole set or a subset of the committers On 25 Jul 2014 00:33, Justin Mclean jus...@classsoftware.com wrote: Hi, As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection. Fair enough + seem reasonable to me. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. You need 3 +1 votes first on the podlings dev list, and PPMC votes do count there, we wouldn't see a lot of podling releases otherwise. :-) Does that mean any +1 vote (say by a committer or user) on the dev list also counts if PPMC votes aren't actually considered binding? (I'd assume not but again it's not clear from the document). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling binding votes
My interpretation (and it's just that) is: Example: Release Vote A podling votes to release (VOTE email to dev@project). The PPMC and IPMC/PPMC (i.e. Mentors) member votes are binding at the PPMC level. This means that those votes are binding and community votes are non-binding. If the PPMC vote passes, the release vote can proceed to the IPMC level (a VOTE email to general@). At this point, PPMC votes are non-binding. Mentor (since mentors are by definition IPMC members) and any non-mentor IPMC member votes can carry over and are binding. Then it's a matter of getting enough additional binding IPMC votes to meet the requirement. At this point, PPMC and community votes are non-binding. Again, this is just my interpretation, and I may be off here. -Taylor On Jul 24, 2014, at 6:57 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Anyone clarify this as it's not mentioned at [1]. Whose votes are binding for releases on the podlings dev list? Obviously mentors and PPMC members, but are IPMC members votes binding? I would assume so but don't see it stated anywhere. Would Apache members votes be binding? Assuming IPMC votes are binding what happen if a podling release dev list vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator or not? Thanks, Justin 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases - 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
Re: Podling binding votes
Sounds right to me. As a separate matter of etiquette and community building, it is usually good form for mentors to vote last during the community vote and first in the IPMC vote. On Thu, Jul 24, 2014 at 8:44 PM, P. Taylor Goetz ptgo...@gmail.com wrote: My interpretation (and it's just that) is: Example: Release Vote A podling votes to release (VOTE email to dev@project). The PPMC and IPMC/PPMC (i.e. Mentors) member votes are binding at the PPMC level. This means that those votes are binding and community votes are non-binding. If the PPMC vote passes, the release vote can proceed to the IPMC level (a VOTE email to general@). At this point, PPMC votes are non-binding. Mentor (since mentors are by definition IPMC members) and any non-mentor IPMC member votes can carry over and are binding. Then it's a matter of getting enough additional binding IPMC votes to meet the requirement. At this point, PPMC and community votes are non-binding. Again, this is just my interpretation, and I may be off here. -Taylor On Jul 24, 2014, at 6:57 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Anyone clarify this as it's not mentioned at [1]. Whose votes are binding for releases on the podlings dev list? Obviously mentors and PPMC members, but are IPMC members votes binding? I would assume so but don't see it stated anywhere. Would Apache members votes be binding? Assuming IPMC votes are binding what happen if a podling release dev list vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator or not? Thanks, Justin 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases - 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
Re: Podling binding votes
Yes, this is what I had seen and recommended to podlings I have been involved with. - Henry On Thu, Jul 24, 2014 at 8:44 PM, P. Taylor Goetz ptgo...@gmail.com wrote: My interpretation (and it's just that) is: Example: Release Vote A podling votes to release (VOTE email to dev@project). The PPMC and IPMC/PPMC (i.e. Mentors) member votes are binding at the PPMC level. This means that those votes are binding and community votes are non-binding. If the PPMC vote passes, the release vote can proceed to the IPMC level (a VOTE email to general@). At this point, PPMC votes are non-binding. Mentor (since mentors are by definition IPMC members) and any non-mentor IPMC member votes can carry over and are binding. Then it's a matter of getting enough additional binding IPMC votes to meet the requirement. At this point, PPMC and community votes are non-binding. Again, this is just my interpretation, and I may be off here. -Taylor On Jul 24, 2014, at 6:57 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Anyone clarify this as it's not mentioned at [1]. Whose votes are binding for releases on the podlings dev list? Obviously mentors and PPMC members, but are IPMC members votes binding? I would assume so but don't see it stated anywhere. Would Apache members votes be binding? Assuming IPMC votes are binding what happen if a podling release dev list vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator or not? Thanks, Justin 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases - 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