justinmclean opened a new pull request #26: reorganise menus
URL: https://github.com/apache/incubator/pull/26
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
justinmclean merged pull request #26: reorganise menus
URL: https://github.com/apache/incubator/pull/26
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
option (D) combined with (E)
And encourage mentors to vote on dev@ makes sense to me
On Fri, Aug 9, 2019 at 3:24 PM Justin Mclean wrote:
> Hi,
>
> > (D) will still require 2 more IPMC vote?
> > (E) will be like (B) in that it will need mentors or other IPMC to vote
> in
> > podling dev@?
>
> Al
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes fine
- LICENSE is fine
- NOTICE may need a little work
- No unexpected binary files
- Source files have ASF headers
- Can compile from source
NOTICE mentions using code From Apache Hive, Apache Lucerne, Apache Hadoop and
A
Hi,
> (D) will still require 2 more IPMC vote?
> (E) will be like (B) in that it will need mentors or other IPMC to vote in
> podling dev@?
All releases require 3 (or more) +1 votes by a PMC so yes they would require 3
IPMC votes.
Thanks,
Justin
-
Links for those who missed the memo (like me)
The current report:
https://cwiki.apache.org/confluence/display/INCUBATOR/August2019
The next report:
https://cwiki.apache.org/confluence/display/INCUBATOR/September2019
On Thu, Aug 8, 2019 at 4:44 PM Justin Mclean
wrote:
> HI,
>
> Of the podlings
(D) will still require 2 more IPMC vote?
(E) will be like (B) in that it will need mentors or other IPMC to vote in
podling dev@?
On Thu, Aug 8, 2019 at 10:04 PM Justin Mclean
wrote:
> Hi,
>
> One of the incubator pain points is the double voting on releases first by
> the podling and then by t