HI,
> based on Justin's and community feedback I'm suggesting to restart the vote.
That wasn’t my suggestion. I was just pointing out you closed the vote too
early.
I'd suggest you fix the issue and call another vote on you dev list and then
bring it back to the incubator to vote, you could pr
+1 binding
Horovod is going to release it's 0.16.0 in the coming week with MXNet
integration. We need to release 1.4.0 which includes all the dependencies
for Horovod integration.
Best,
Lin
On Mon, Feb 11, 2019 at 9:30 PM Steffen Rochel
wrote:
> Dear community -
> based on Justin's and communi
Dear community -
based on Justin's and community feedback I'm suggesting to restart the vote.
Current status:
binding votes:
+1: 2 votes (Henri, Jason)
-1: 1 vote (Luciano)
non-binding:
+1: 1 vote (Kellen)
The community is investigating feedback from Luciano that the exclusion
file is to broad a
On Mon, Feb 11, 2019 at 3:55 PM Hen wrote:
>
> Did you mean:
>
> "The rat-exclude configuration on the project _must_ be less permissive."
>
> ?
>
What I was trying to say is that, even though MXNet has configured and
is using rat, the rat-exclude then is very broad, where it excludes
like (*.xml
Did you mean:
"The rat-exclude configuration on the project _must_ be less permissive."
?
(your text suggests it's an option, whereas your vote says it's required)
On Sun, Feb 10, 2019 at 8:08 PM Luciano Resende
wrote:
> I ran RAT, and while I understand that a lot of the failures are
> comin
Based on Justin's feedback, can we resume the vote instead of cancelling it?
On Mon, Feb 11, 2019 at 12:02 AM Justin Mclean
wrote:
> Hi,
>
> In future don’t be so hasty to cancel a release vote, people mind can be
> changed and a -1 is not a veto on a release.
>
> Thanks,
> Justin
>
>
>
Thanks Pierre. Sorry, I was trying to spare myself looking ignorant, and I
ended up breaking public comms.
Thanks for the advice, I’ll proceed.
> On Feb 11, 2019, at 12:28 AM, Pierre Smits wrote:
>
> Hi Antoine,
>
> I suggest to include the general@incubator.a.o mailing list as it will allow
And building awareness, reputation and community around something is quite a
lot of work.
So If you start a new podling and work hard on promoting it, it would be a
shame having to rename that and effectively loose all promotional results you
might have had.
I would also strongly suggest to do
Hi,
A name search is not needed before going the incubator, however changing a
project name does have a cost both infra wise and community wise, so it be to
come up with a name that likely be unique in project the project does.
Thanks,
Justin
Hi Antoine,
I suggest to include the general@incubator.a.o mailing list as it will
allow other Apache contributors to chime in (maybe even faster than I am).
Regarding the search for the optimal name, the best way to go about (IMO)
is to make a short list - in accordance with [1] - and discuss th
Hi,
In future don’t be so hasty to cancel a release vote, people mind can be
changed and a -1 is not a veto on a release.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional command
11 matches
Mail list logo
