RE: Slack Subscribe

2017-10-30 Thread Tyler Kvochick 
Yep! Thank you

-Original Message-
From: Hen [mailto:bay...@apache.org] 
Sent: Monday, October 30, 2017 5:22 PM
To: dev@mxnet.incubator.apache.org
Subject: Re: Slack Subscribe

Looks like someone has sent you an invite.

(Folk, please let the list know when you've invited, otherwise N other people 
will burn time; apologies if whomever invited was doing it at exactly the same 
time).

On Mon, Oct 30, 2017 at 4:55 PM, Tyler Kvochick 
wrote:

> Hello,
>
> Trying to subscribe to the MXnet slack channel.
>
> thanks
>

Re: Slack Subscribe

2017-10-30 Thread Hen 
Looks like someone has sent you an invite.

(Folk, please let the list know when you've invited, otherwise N other
people will burn time; apologies if whomever invited was doing it at
exactly the same time).

On Mon, Oct 30, 2017 at 4:55 PM, Tyler Kvochick 
wrote:

> Hello,
>
> Trying to subscribe to the MXnet slack channel.
>
> thanks
>

Slack Subscribe

2017-10-30 Thread Tyler Kvochick 
Hello,

Trying to subscribe to the MXnet slack channel.

thanks

Re: Draft of blog post for MXNet v0.12 release

2017-10-30 Thread Suk Won Kim 
Yes,
I have been in touch with Sally for this post, and she is aware of this.
It will not be published via official press release.

On Mon, Oct 30, 2017 at 4:10 PM, Chris Mattmann  wrote:

> Has this been in coordination with Sally? There’s a pretty hard and fast
> Incubator rule to not promote
> Podlings via official press channels – where will this be published?
>
> Cheers,
> Chris
>
>
>
>
> On 10/30/17, 4:08 PM, "Suk Won Kim"  wrote:
>
> Created a page in cwiki for a draft of blog post for MXNet v0.12
> release.
> https://cwiki.apache.org/confluence/display/MXNET/
> Draft+of+blog+post+for+MXNet+v0.12+release
>
> Thanks.
> --
>
> *Sukwon Kim, *
>
>
>
>


-- 

*Sukwon Kim, *

Senior Product Manager-Technical,
Amazon Web Services (AWS) EC2

Draft of blog post for MXNet v0.12 release

2017-10-30 Thread Suk Won Kim 
Created a page in cwiki for a draft of blog post for MXNet v0.12 release.
https://cwiki.apache.org/confluence/display/MXNET/Draft+of+blog+post+for+MXNet+v0.12+release

Thanks.
-- 

*Sukwon Kim, *

Re: MXNet blog for upcoming release

2017-10-30 Thread Hen 
https://issues.apache.org/jira/browse/INFRA-15407

On Mon, Oct 30, 2017 at 12:12 PM, Hen  wrote:

> Having a blog for the project sounds like a good idea.
>
> I don't see one already existing, and I see other incubator podlings with
> a blog, so I'll go ahead and open a JIRA.
>
> Hen
>
> On Mon, Oct 30, 2017 at 9:29 AM, Suk Won Kim  wrote:
>
>> Hi all,
>> Meghna is going to execute the MXNet v0.12 release on 10/31.
>> I'd like to help her with creating MXNet blog for it.
>> Can you please point me to the instructions how to create a blog?
>> Thanks!
>>
>>
>> --
>>
>> *Sukwon Kim, *
>>
>
>

Re: MXNet blog for upcoming release

2017-10-30 Thread Hen 
Having a blog for the project sounds like a good idea.

I don't see one already existing, and I see other incubator podlings with a
blog, so I'll go ahead and open a JIRA.

Hen

On Mon, Oct 30, 2017 at 9:29 AM, Suk Won Kim  wrote:

> Hi all,
> Meghna is going to execute the MXNet v0.12 release on 10/31.
> I'd like to help her with creating MXNet blog for it.
> Can you please point me to the instructions how to create a blog?
> Thanks!
>
>
> --
>
> *Sukwon Kim, *
>

Re: Request for an invite to MXNet slack channel

2017-10-30 Thread Steffen Rochel 
Done
On Mon, Oct 30, 2017 at 5:04 PM Suk Won Kim  wrote:

> Hello,
> Please send me an invite to the MXNet Slack Channel ASAP.
> Thanks!
>
> --
>
> *Sukwon Kim, *
>

Re: [Proposal] Stabilizing Apache MXNet CI build system

2017-10-30 Thread Hen 
How about we ask for a new mxnet repo to store all the config in?

On Fri, Oct 27, 2017 at 05:30 Pedro Larroy 
wrote:

> Just to provide a high level overview of the ideas and proposals
> coming from different sources for the requirements for testing and
> validation of builds:
>
> * Have terraform files for the testing infrastructure. Infrastructure
> as code (IaC). Minus not emulated / nor cloud based, embedded
> hardware. ("single command" replication of the testing infrastructure,
> no manual steps).
>
> * CI software based on Jenkins, unless someone thinks there's a better
> alternative.
>
> * Use autoscaling groups and improve staggered build + test steps to
> achieve higher parallelism and shorter feedback times.
>
> * Switch to a branching model based on stable master + integration
> branch. PRs are merged into dev/integration which runs extended
> nightly tests, which are
> then merged into master, preferably in an automated way after
> successful extended testing.
> Master is always tested, and always buildable. Release branches or
> tags in master as usual for releases.
>
> * Build + test feedback time targeting less than 15 minutes.
> (Currently a build in a 16x core takes 7m). This involves lot of
> refactoring of tests, move expensive tests / big smoke tests to
> nightlies on the integration branch, also tests on IoT devices / power
> and performance regressions...
>
> * Add code coverage and other quality metrics.
>
> * Eliminate warnings and treat warnings as errors. We have spent time
> tracking down "undefined behaviour" bugs that could have been caught
> by compiler warnings.
>
> Is there something I'm missing or additional things that come to your
> mind that you would wish to add?
>
> Pedro.
>

Request for an invite to MXNet slack channel

2017-10-30 Thread Suk Won Kim 
Hello,
Please send me an invite to the MXNet Slack Channel ASAP.
Thanks!

-- 

*Sukwon Kim, *