Re: Code freeze for 1.5.1 patch release

[Tao Lv]

I have started the voting thread and move the language binding to after the
vote passes.
If someone has concerns about this decision, please comment in the voting
thread.

Thanks,
-tao

On Wed, Sep 18, 2019 at 1:09 AM Carin Meier  wrote:

> To clarify, the Clojure source is included is the vote, the built jar is
> not
>
> On Tue, Sep 17, 2019 at 1:08 PM Carin Meier  wrote:
>
> > We have done that on other releases. That is, vote without Clojure
> > package. Someone feel free to clarify the official stance.
> >
> > On Tue, Sep 17, 2019 at 12:55 PM Lin Yuan  wrote:
> >
> >> Hi Tao,
> >>
> >> If the voting is on the source and not requiring the language bindings,
> >> can
> >> we do the voting in parallel with the release?
> >>
> >> Carin/Qing, please help to clarify if the R/Clojure language bindings
> are
> >> required for voting.
> >>
> >> Thanks,
> >>
> >> Lin
> >>
> >> On Tue, Sep 17, 2019 at 7:32 AM Tao Lv  wrote:
> >>
> >> > Thanks for your help, Carin. Per step 1.14 of  the release process
> [1],
> >> > stage repo links should be included in the voting email.
> >> >
> >> > Scala packages are done. Thanks to the help from @Lanking.
> >> >
> >> > We still have problem with R package on Windows. @yajiedesign is
> >> helping on
> >> > that.
> >> >
> >> > Again thanks for all of your support and patience.
> >> >
> >> > -tao
> >> >
> >> > [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> >> >
> >> > On Tue, Sep 17, 2019 at 6:10 PM Carin Meier 
> >> wrote:
> >> >
> >> > > I will be able to build the Clojure packages on Friday. I don’t
> >> believe
> >> > > this needs to hold up the voting. I believe the voting is only on
> the
> >> > > source.
> >> > >
> >> > > -Carin
> >> > >
> >> > > On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan 
> wrote:
> >> > >
> >> > > > Hi Tao,
> >> > > >
> >> > > > Thanks for uploading the artifacts. May I know what the current
> >> status
> >> > of
> >> > > > Scala, Clojure and R packages and any help you need from the
> >> community
> >> > to
> >> > > > complete?
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > Lin
> >> > > >
> >> > > > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
> >> > > >
> >> > > > > Update:
> >> > > > >
> >> > > > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache
> >> dist.
> >> > > > Before
> >> > > > > voting, we still need some time to build packages for Scala,
> >> Clojure
> >> > > and
> >> > > > R.
> >> > > > >
> >> > > > > Thank you for your patience.
> >> > > > >
> >> > > > > -tao
> >> > > > >
> >> > > > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv 
> wrote:
> >> > > > >
> >> > > > > >
> >> > > > > > Following the release process [1], I just created the tag for
> >> > > 1.5.1.rc0
> >> > > > > > [2]. Artifacts uploading and validation are still WIP. Will
> keep
> >> > you
> >> > > > > > posted. Hopefully we can start the veto soon for a new
> release.
> >> :)
> >> > > > > >
> >> > > > > > Let me know if you any question or suggestion for the release.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > -tao
> >> > > > > >
> >> > > > > > [1]
> >> > > https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> >> > > > > > [2]
> >> > https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv 
> wrote:
> >> > > > > >
> >> > > > > >>
> >> > > > > >> Code freezing!
> >> > > > > >>
> >> > > > > >> If you happen to be around github, please help to review the
> PR
> >> > [1]
> >> > > > for
> >> > > > > >> bumping version strings on the release branch. Thanks.
> >> > > > > >>
> >> > > > > >> I will continue working on the rest steps for the release.
> >> > > > > >>
> >> > > > > >> Thanks,
> >> > > > > >> -tao
> >> > > > > >>
> >> > > > > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
> >> > > > > >>
> >> > > > > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv 
> >> wrote:
> >> > > > > >>
> >> > > > > >>>
> >> > > > > >>> I drafted the release notes for 1.5.1 patch release:
> >> > > > > >>>
> >> > > >
> >> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> >> > > > > >>>
> >> > > > > >>> Any comments or suggestions are highly appreciated!
> >> > > > > >>>
> >> > > > > >>> -tao
> >> > > > > >>>
> >> > > > > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> >> > > > > >>> kellen.sunderl...@gmail.com> wrote:
> >> > > > > >>>
> >> > > > >  Thanks for organizing the release Tao.
> >> > > > > 
> >> > > > >  On Sun, Sep 1, 2019, 5:53 PM Tao Lv 
> >> wrote:
> >> > > > > 
> >> > > > >  > Hi Community,
> >> > > > >  >
> >> > > > >  > Code freeze for 1.5.1 patch release will be 9/3 6pm PST
> >> (9/4
> >> > 9am
> >> > > > >  CST). If
> >> > > > >  > you have any additional fix in progress and would like to
> >> > > include
> >> > > > it
> >> > > > >  in
> >> > > > >  > this release, please assure they have been merged before
> >> code
> >> > > > > freeze.
> >> > > > > 

Re: [VOTE] Release Apache MXNet (incubating) 1.5.1.rc0

[Qing Lan]

+1 for Scala/Java test. Passed all tests for CPU/GPU build.
Also tested build from source with static build.

Thanks,
Qing

From: Tao Lv 
Sent: Tuesday, September 17, 2019 14:14
To: dev@mxnet.incubator.apache.org 
Subject: [VOTE] Release Apache MXNet (incubating) 1.5.1.rc0

Dear MXNet community,



This is the 3-day vote to release Apache MXNet (incubating) version 1.5.1.

Voting on dev@ will start September 17, 12:00pm (PST)  and close on
September 20, 12:00pm (PST).



1) Link to release notes:

https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes



2) Link to release candidate:

https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0



3) Link to source and signatures on Apache dist server:

https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.1.rc0/



Please remember to TEST first before voting accordingly:

+1 = approve

+0 = no opinion

-1 = disapprove (provide reason)



Thanks,

-tao

[VOTE] Release Apache MXNet (incubating) 1.5.1.rc0

[Tao Lv]

Dear MXNet community,



This is the 3-day vote to release Apache MXNet (incubating) version 1.5.1.

Voting on dev@ will start September 17, 12:00pm (PST)  and close on
September 20, 12:00pm (PST).



1) Link to release notes:

https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes



2) Link to release candidate:

https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0



3) Link to source and signatures on Apache dist server:

https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.1.rc0/



Please remember to TEST first before voting accordingly:

+1 = approve

+0 = no opinion

-1 = disapprove (provide reason)



Thanks,

-tao

Re: Code freeze for 1.5.1 patch release

[Carin Meier]

To clarify, the Clojure source is included is the vote, the built jar is not

On Tue, Sep 17, 2019 at 1:08 PM Carin Meier  wrote:

> We have done that on other releases. That is, vote without Clojure
> package. Someone feel free to clarify the official stance.
>
> On Tue, Sep 17, 2019 at 12:55 PM Lin Yuan  wrote:
>
>> Hi Tao,
>>
>> If the voting is on the source and not requiring the language bindings,
>> can
>> we do the voting in parallel with the release?
>>
>> Carin/Qing, please help to clarify if the R/Clojure language bindings are
>> required for voting.
>>
>> Thanks,
>>
>> Lin
>>
>> On Tue, Sep 17, 2019 at 7:32 AM Tao Lv  wrote:
>>
>> > Thanks for your help, Carin. Per step 1.14 of  the release process [1],
>> > stage repo links should be included in the voting email.
>> >
>> > Scala packages are done. Thanks to the help from @Lanking.
>> >
>> > We still have problem with R package on Windows. @yajiedesign is
>> helping on
>> > that.
>> >
>> > Again thanks for all of your support and patience.
>> >
>> > -tao
>> >
>> > [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
>> >
>> > On Tue, Sep 17, 2019 at 6:10 PM Carin Meier 
>> wrote:
>> >
>> > > I will be able to build the Clojure packages on Friday. I don’t
>> believe
>> > > this needs to hold up the voting. I believe the voting is only on the
>> > > source.
>> > >
>> > > -Carin
>> > >
>> > > On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan  wrote:
>> > >
>> > > > Hi Tao,
>> > > >
>> > > > Thanks for uploading the artifacts. May I know what the current
>> status
>> > of
>> > > > Scala, Clojure and R packages and any help you need from the
>> community
>> > to
>> > > > complete?
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Lin
>> > > >
>> > > > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
>> > > >
>> > > > > Update:
>> > > > >
>> > > > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache
>> dist.
>> > > > Before
>> > > > > voting, we still need some time to build packages for Scala,
>> Clojure
>> > > and
>> > > > R.
>> > > > >
>> > > > > Thank you for your patience.
>> > > > >
>> > > > > -tao
>> > > > >
>> > > > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:
>> > > > >
>> > > > > >
>> > > > > > Following the release process [1], I just created the tag for
>> > > 1.5.1.rc0
>> > > > > > [2]. Artifacts uploading and validation are still WIP. Will keep
>> > you
>> > > > > > posted. Hopefully we can start the veto soon for a new release.
>> :)
>> > > > > >
>> > > > > > Let me know if you any question or suggestion for the release.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > -tao
>> > > > > >
>> > > > > > [1]
>> > > https://cwiki.apache.org/confluence/display/MXNET/Release+Process
>> > > > > > [2]
>> > https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
>> > > > > >
>> > > > > >
>> > > > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
>> > > > > >
>> > > > > >>
>> > > > > >> Code freezing!
>> > > > > >>
>> > > > > >> If you happen to be around github, please help to review the PR
>> > [1]
>> > > > for
>> > > > > >> bumping version strings on the release branch. Thanks.
>> > > > > >>
>> > > > > >> I will continue working on the rest steps for the release.
>> > > > > >>
>> > > > > >> Thanks,
>> > > > > >> -tao
>> > > > > >>
>> > > > > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
>> > > > > >>
>> > > > > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv 
>> wrote:
>> > > > > >>
>> > > > > >>>
>> > > > > >>> I drafted the release notes for 1.5.1 patch release:
>> > > > > >>>
>> > > >
>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
>> > > > > >>>
>> > > > > >>> Any comments or suggestions are highly appreciated!
>> > > > > >>>
>> > > > > >>> -tao
>> > > > > >>>
>> > > > > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
>> > > > > >>> kellen.sunderl...@gmail.com> wrote:
>> > > > > >>>
>> > > > >  Thanks for organizing the release Tao.
>> > > > > 
>> > > > >  On Sun, Sep 1, 2019, 5:53 PM Tao Lv 
>> wrote:
>> > > > > 
>> > > > >  > Hi Community,
>> > > > >  >
>> > > > >  > Code freeze for 1.5.1 patch release will be 9/3 6pm PST
>> (9/4
>> > 9am
>> > > > >  CST). If
>> > > > >  > you have any additional fix in progress and would like to
>> > > include
>> > > > it
>> > > > >  in
>> > > > >  > this release, please assure they have been merged before
>> code
>> > > > > freeze.
>> > > > >  >
>> > > > >  > Thanks for all your support and contribution.
>> > > > >  >
>> > > > >  > -tao
>> > > > >  >
>> > > > > 
>> > > > > >>>
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: Code freeze for 1.5.1 patch release

[Carin Meier]

We have done that on other releases. That is, vote without Clojure package.
Someone feel free to clarify the official stance.

On Tue, Sep 17, 2019 at 12:55 PM Lin Yuan  wrote:

> Hi Tao,
>
> If the voting is on the source and not requiring the language bindings, can
> we do the voting in parallel with the release?
>
> Carin/Qing, please help to clarify if the R/Clojure language bindings are
> required for voting.
>
> Thanks,
>
> Lin
>
> On Tue, Sep 17, 2019 at 7:32 AM Tao Lv  wrote:
>
> > Thanks for your help, Carin. Per step 1.14 of  the release process [1],
> > stage repo links should be included in the voting email.
> >
> > Scala packages are done. Thanks to the help from @Lanking.
> >
> > We still have problem with R package on Windows. @yajiedesign is helping
> on
> > that.
> >
> > Again thanks for all of your support and patience.
> >
> > -tao
> >
> > [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> >
> > On Tue, Sep 17, 2019 at 6:10 PM Carin Meier 
> wrote:
> >
> > > I will be able to build the Clojure packages on Friday. I don’t believe
> > > this needs to hold up the voting. I believe the voting is only on the
> > > source.
> > >
> > > -Carin
> > >
> > > On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan  wrote:
> > >
> > > > Hi Tao,
> > > >
> > > > Thanks for uploading the artifacts. May I know what the current
> status
> > of
> > > > Scala, Clojure and R packages and any help you need from the
> community
> > to
> > > > complete?
> > > >
> > > > Thanks,
> > > >
> > > > Lin
> > > >
> > > > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
> > > >
> > > > > Update:
> > > > >
> > > > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache
> dist.
> > > > Before
> > > > > voting, we still need some time to build packages for Scala,
> Clojure
> > > and
> > > > R.
> > > > >
> > > > > Thank you for your patience.
> > > > >
> > > > > -tao
> > > > >
> > > > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:
> > > > >
> > > > > >
> > > > > > Following the release process [1], I just created the tag for
> > > 1.5.1.rc0
> > > > > > [2]. Artifacts uploading and validation are still WIP. Will keep
> > you
> > > > > > posted. Hopefully we can start the veto soon for a new release.
> :)
> > > > > >
> > > > > > Let me know if you any question or suggestion for the release.
> > > > > >
> > > > > > Thanks,
> > > > > > -tao
> > > > > >
> > > > > > [1]
> > > https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > > > > > [2]
> > https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> > > > > >
> > > > > >
> > > > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
> > > > > >
> > > > > >>
> > > > > >> Code freezing!
> > > > > >>
> > > > > >> If you happen to be around github, please help to review the PR
> > [1]
> > > > for
> > > > > >> bumping version strings on the release branch. Thanks.
> > > > > >>
> > > > > >> I will continue working on the rest steps for the release.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> -tao
> > > > > >>
> > > > > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
> > > > > >>
> > > > > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
> > > > > >>
> > > > > >>>
> > > > > >>> I drafted the release notes for 1.5.1 patch release:
> > > > > >>>
> > > >
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> > > > > >>>
> > > > > >>> Any comments or suggestions are highly appreciated!
> > > > > >>>
> > > > > >>> -tao
> > > > > >>>
> > > > > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> > > > > >>> kellen.sunderl...@gmail.com> wrote:
> > > > > >>>
> > > > >  Thanks for organizing the release Tao.
> > > > > 
> > > > >  On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
> > > > > 
> > > > >  > Hi Community,
> > > > >  >
> > > > >  > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4
> > 9am
> > > > >  CST). If
> > > > >  > you have any additional fix in progress and would like to
> > > include
> > > > it
> > > > >  in
> > > > >  > this release, please assure they have been merged before
> code
> > > > > freeze.
> > > > >  >
> > > > >  > Thanks for all your support and contribution.
> > > > >  >
> > > > >  > -tao
> > > > >  >
> > > > > 
> > > > > >>>
> > > > >
> > > >
> > >
> >
>

Re: Code freeze for 1.5.1 patch release

[Lin Yuan]

Hi Tao,

If the voting is on the source and not requiring the language bindings, can
we do the voting in parallel with the release?

Carin/Qing, please help to clarify if the R/Clojure language bindings are
required for voting.

Thanks,

Lin

On Tue, Sep 17, 2019 at 7:32 AM Tao Lv  wrote:

> Thanks for your help, Carin. Per step 1.14 of  the release process [1],
> stage repo links should be included in the voting email.
>
> Scala packages are done. Thanks to the help from @Lanking.
>
> We still have problem with R package on Windows. @yajiedesign is helping on
> that.
>
> Again thanks for all of your support and patience.
>
> -tao
>
> [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
>
> On Tue, Sep 17, 2019 at 6:10 PM Carin Meier  wrote:
>
> > I will be able to build the Clojure packages on Friday. I don’t believe
> > this needs to hold up the voting. I believe the voting is only on the
> > source.
> >
> > -Carin
> >
> > On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan  wrote:
> >
> > > Hi Tao,
> > >
> > > Thanks for uploading the artifacts. May I know what the current status
> of
> > > Scala, Clojure and R packages and any help you need from the community
> to
> > > complete?
> > >
> > > Thanks,
> > >
> > > Lin
> > >
> > > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
> > >
> > > > Update:
> > > >
> > > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist.
> > > Before
> > > > voting, we still need some time to build packages for Scala, Clojure
> > and
> > > R.
> > > >
> > > > Thank you for your patience.
> > > >
> > > > -tao
> > > >
> > > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:
> > > >
> > > > >
> > > > > Following the release process [1], I just created the tag for
> > 1.5.1.rc0
> > > > > [2]. Artifacts uploading and validation are still WIP. Will keep
> you
> > > > > posted. Hopefully we can start the veto soon for a new release. :)
> > > > >
> > > > > Let me know if you any question or suggestion for the release.
> > > > >
> > > > > Thanks,
> > > > > -tao
> > > > >
> > > > > [1]
> > https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > > > > [2]
> https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> > > > >
> > > > >
> > > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
> > > > >
> > > > >>
> > > > >> Code freezing!
> > > > >>
> > > > >> If you happen to be around github, please help to review the PR
> [1]
> > > for
> > > > >> bumping version strings on the release branch. Thanks.
> > > > >>
> > > > >> I will continue working on the rest steps for the release.
> > > > >>
> > > > >> Thanks,
> > > > >> -tao
> > > > >>
> > > > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
> > > > >>
> > > > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
> > > > >>
> > > > >>>
> > > > >>> I drafted the release notes for 1.5.1 patch release:
> > > > >>>
> > > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> > > > >>>
> > > > >>> Any comments or suggestions are highly appreciated!
> > > > >>>
> > > > >>> -tao
> > > > >>>
> > > > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> > > > >>> kellen.sunderl...@gmail.com> wrote:
> > > > >>>
> > > >  Thanks for organizing the release Tao.
> > > > 
> > > >  On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
> > > > 
> > > >  > Hi Community,
> > > >  >
> > > >  > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4
> 9am
> > > >  CST). If
> > > >  > you have any additional fix in progress and would like to
> > include
> > > it
> > > >  in
> > > >  > this release, please assure they have been merged before code
> > > > freeze.
> > > >  >
> > > >  > Thanks for all your support and contribution.
> > > >  >
> > > >  > -tao
> > > >  >
> > > > 
> > > > >>>
> > > >
> > >
> >
>

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

Thanks for your help, Carin. Per step 1.14 of  the release process [1],
stage repo links should be included in the voting email.

Scala packages are done. Thanks to the help from @Lanking.

We still have problem with R package on Windows. @yajiedesign is helping on
that.

Again thanks for all of your support and patience.

-tao

[1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process

On Tue, Sep 17, 2019 at 6:10 PM Carin Meier  wrote:

> I will be able to build the Clojure packages on Friday. I don’t believe
> this needs to hold up the voting. I believe the voting is only on the
> source.
>
> -Carin
>
> On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan  wrote:
>
> > Hi Tao,
> >
> > Thanks for uploading the artifacts. May I know what the current status of
> > Scala, Clojure and R packages and any help you need from the community to
> > complete?
> >
> > Thanks,
> >
> > Lin
> >
> > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
> >
> > > Update:
> > >
> > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist.
> > Before
> > > voting, we still need some time to build packages for Scala, Clojure
> and
> > R.
> > >
> > > Thank you for your patience.
> > >
> > > -tao
> > >
> > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:
> > >
> > > >
> > > > Following the release process [1], I just created the tag for
> 1.5.1.rc0
> > > > [2]. Artifacts uploading and validation are still WIP. Will keep you
> > > > posted. Hopefully we can start the veto soon for a new release. :)
> > > >
> > > > Let me know if you any question or suggestion for the release.
> > > >
> > > > Thanks,
> > > > -tao
> > > >
> > > > [1]
> https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > > > [2] https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> > > >
> > > >
> > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
> > > >
> > > >>
> > > >> Code freezing!
> > > >>
> > > >> If you happen to be around github, please help to review the PR [1]
> > for
> > > >> bumping version strings on the release branch. Thanks.
> > > >>
> > > >> I will continue working on the rest steps for the release.
> > > >>
> > > >> Thanks,
> > > >> -tao
> > > >>
> > > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
> > > >>
> > > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
> > > >>
> > > >>>
> > > >>> I drafted the release notes for 1.5.1 patch release:
> > > >>>
> > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> > > >>>
> > > >>> Any comments or suggestions are highly appreciated!
> > > >>>
> > > >>> -tao
> > > >>>
> > > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> > > >>> kellen.sunderl...@gmail.com> wrote:
> > > >>>
> > >  Thanks for organizing the release Tao.
> > > 
> > >  On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
> > > 
> > >  > Hi Community,
> > >  >
> > >  > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am
> > >  CST). If
> > >  > you have any additional fix in progress and would like to
> include
> > it
> > >  in
> > >  > this release, please assure they have been merged before code
> > > freeze.
> > >  >
> > >  > Thanks for all your support and contribution.
> > >  >
> > >  > -tao
> > >  >
> > > 
> > > >>>
> > >
> >
>

Re: [DISCUSS] CI Access Control

[Marco de Abreu]

Ah, with regards to #1 and #2: Currently, we don't have any plugins that
control the actions of a single user and allows us to monitor and rate
limit them. Just giving trigger permission (which is also tied with
abort-permission if I recall correctly), would allow a malicious user to
start a huge number of jobs and thus either create immense costs or bring
down the system. Also, we'd have to check how we can restrict the trigger
permission to specific jobs.

-Marco

On Tue, Sep 17, 2019 at 2:47 PM Marco de Abreu 
wrote:

> Hi Sheng,
>
> will I'm in general all in favour of widening the access to distribute the
> tasks, the situation around the CI system in particular is a bit more
> difficult.
>
> As far as I know, the creation of the CI system is neither automated,
> versioned nor backed up or safeguarded. This means that if somebody makes a
> change that breaks something, we're left with a broken system we can't
> recover from. Thus, I preferred it in the past to restrict the access as
> much as possible (at least to Prod) to avoid these situations from
> happening. While #1 and #2 are already possible today (we have two roles
> for committers and regular users that allow this already), #3 and #4 come
> with a significant risk for the stability of the system.
>
> As soon as a job is added or changed, a lot of things happen in Jenkins -
> one of these tasks is the SCM scan which tries to determine the branches
> the job should run on. For somebody who is inexperienced, the first pitfall
> is that suddenly hundreds of jobs are being spawned which will certainly
> overload Jenkins and render it unusable. There are a lot of tricks and I
> could elaborate them, but basically the bottom line is that the
> configuration interface of Jenkins is far from fail-proof and exposes a
> significant risk if accessed by somebody who doesn't exactly know what
> they're doing - speak, we would need to design some kind of training and
> even that would not safeguard us from these fatal events.
>
> There's the whole security aspect around user-facing artifact generation
> of CI/CD and the possibility of them being tampered, but I don't think I
> have to elaborate that.
>
> With regards to #4 especially, I'd say that the risk of somebody just
> upgrading the system or changing plugins inherits an even bigger risk.
> Plugins are notoriously unsafe and system updates have also shown to not
> really go like a breeze. I'd argue that changes to the system should only
> be done by the administrators of it since they have a bigger overview over
> all the things that are currently going on while also having the full
> access (backups before making changes, SSH access, log access, metric
> access, etc) to debug errors. In the end we shouldn't forget that this is a
> productive system - usually, you'd have nobody being able to touch it at
> all, but we're not in a perfect world, so I'd say we should restrict it to
> a bare minimum in the form of admins.
>
> So while I certainly understand and encourage to distribute the access, I
> don't feel comfortable widening the access to such a critical productive
> system. It being down means that the GitHub development is fully halted,
> which is really problematic since we don't have rollback mechanisms.
>
> Best regards,
> marco
>
> On Sun, Sep 15, 2019 at 6:40 AM Sheng Zha  wrote:
>
>> Hi,
>>
>> I'd like to initiate discussion on how access control should be managed
>> for the CI system. The hope is that we can present the conclusion of this
>> discussion as the recommendation and request to the donors of the CI system
>> from Amazon.
>>
>> The specific aspects I'd like to discuss are the abilities to:
>> 1. trigger PR validation and nightly jobs.
>> 2. trigger continuous delivery jobs, such as for binary releases in pip,
>> maven, and dockerhub.
>> 3. add jobs to the CI system.
>> 4. maintain and manage the CI system, such as system upgrades and jenkins
>> plugin installation.
>>
>> Given that we already have GitHub SSO enabled on the Jenkins CI, I
>> suggest the following authentication levels for these items:
>> 1. all authenticated GitHub users.
>> 2-4. all MXNet committers
>>
>> What do you think? If you have more aspects that you wish to discuss,
>> feel free to propose.
>>
>> -sz
>>
>

Re: [DISCUSS] CI Access Control

[Marco de Abreu]

Hi Sheng,

will I'm in general all in favour of widening the access to distribute the
tasks, the situation around the CI system in particular is a bit more
difficult.

As far as I know, the creation of the CI system is neither automated,
versioned nor backed up or safeguarded. This means that if somebody makes a
change that breaks something, we're left with a broken system we can't
recover from. Thus, I preferred it in the past to restrict the access as
much as possible (at least to Prod) to avoid these situations from
happening. While #1 and #2 are already possible today (we have two roles
for committers and regular users that allow this already), #3 and #4 come
with a significant risk for the stability of the system.

As soon as a job is added or changed, a lot of things happen in Jenkins -
one of these tasks is the SCM scan which tries to determine the branches
the job should run on. For somebody who is inexperienced, the first pitfall
is that suddenly hundreds of jobs are being spawned which will certainly
overload Jenkins and render it unusable. There are a lot of tricks and I
could elaborate them, but basically the bottom line is that the
configuration interface of Jenkins is far from fail-proof and exposes a
significant risk if accessed by somebody who doesn't exactly know what
they're doing - speak, we would need to design some kind of training and
even that would not safeguard us from these fatal events.

There's the whole security aspect around user-facing artifact generation of
CI/CD and the possibility of them being tampered, but I don't think I have
to elaborate that.

With regards to #4 especially, I'd say that the risk of somebody just
upgrading the system or changing plugins inherits an even bigger risk.
Plugins are notoriously unsafe and system updates have also shown to not
really go like a breeze. I'd argue that changes to the system should only
be done by the administrators of it since they have a bigger overview over
all the things that are currently going on while also having the full
access (backups before making changes, SSH access, log access, metric
access, etc) to debug errors. In the end we shouldn't forget that this is a
productive system - usually, you'd have nobody being able to touch it at
all, but we're not in a perfect world, so I'd say we should restrict it to
a bare minimum in the form of admins.

So while I certainly understand and encourage to distribute the access, I
don't feel comfortable widening the access to such a critical productive
system. It being down means that the GitHub development is fully halted,
which is really problematic since we don't have rollback mechanisms.

Best regards,
marco

On Sun, Sep 15, 2019 at 6:40 AM Sheng Zha  wrote:

> Hi,
>
> I'd like to initiate discussion on how access control should be managed
> for the CI system. The hope is that we can present the conclusion of this
> discussion as the recommendation and request to the donors of the CI system
> from Amazon.
>
> The specific aspects I'd like to discuss are the abilities to:
> 1. trigger PR validation and nightly jobs.
> 2. trigger continuous delivery jobs, such as for binary releases in pip,
> maven, and dockerhub.
> 3. add jobs to the CI system.
> 4. maintain and manage the CI system, such as system upgrades and jenkins
> plugin installation.
>
> Given that we already have GitHub SSO enabled on the Jenkins CI, I suggest
> the following authentication levels for these items:
> 1. all authenticated GitHub users.
> 2-4. all MXNet committers
>
> What do you think? If you have more aspects that you wish to discuss, feel
> free to propose.
>
> -sz
>

Re: Code freeze for 1.5.1 patch release

[Carin Meier]

I will be able to build the Clojure packages on Friday. I don’t believe
this needs to hold up the voting. I believe the voting is only on the
source.

-Carin

On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan  wrote:

> Hi Tao,
>
> Thanks for uploading the artifacts. May I know what the current status of
> Scala, Clojure and R packages and any help you need from the community to
> complete?
>
> Thanks,
>
> Lin
>
> On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
>
> > Update:
> >
> > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist.
> Before
> > voting, we still need some time to build packages for Scala, Clojure and
> R.
> >
> > Thank you for your patience.
> >
> > -tao
> >
> > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:
> >
> > >
> > > Following the release process [1], I just created the tag for 1.5.1.rc0
> > > [2]. Artifacts uploading and validation are still WIP. Will keep you
> > > posted. Hopefully we can start the veto soon for a new release. :)
> > >
> > > Let me know if you any question or suggestion for the release.
> > >
> > > Thanks,
> > > -tao
> > >
> > > [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > > [2] https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> > >
> > >
> > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
> > >
> > >>
> > >> Code freezing!
> > >>
> > >> If you happen to be around github, please help to review the PR [1]
> for
> > >> bumping version strings on the release branch. Thanks.
> > >>
> > >> I will continue working on the rest steps for the release.
> > >>
> > >> Thanks,
> > >> -tao
> > >>
> > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
> > >>
> > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
> > >>
> > >>>
> > >>> I drafted the release notes for 1.5.1 patch release:
> > >>>
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> > >>>
> > >>> Any comments or suggestions are highly appreciated!
> > >>>
> > >>> -tao
> > >>>
> > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> > >>> kellen.sunderl...@gmail.com> wrote:
> > >>>
> >  Thanks for organizing the release Tao.
> > 
> >  On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
> > 
> >  > Hi Community,
> >  >
> >  > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am
> >  CST). If
> >  > you have any additional fix in progress and would like to include
> it
> >  in
> >  > this release, please assure they have been merged before code
> > freeze.
> >  >
> >  > Thanks for all your support and contribution.
> >  >
> >  > -tao
> >  >
> > 
> > >>>
> >
>

[Call for Contributions] NumPy operators in MXNet

[Jun Wu]

Dear Community,

As part of the scope towards MXNet 2.0 (see the RFC
), we have been
putting a lot of efforts on implementing NumPy operators in MXNet. Over the
past three months, we have implemented about 140 NumPy operators, of which
80 have been merged and the rest are in code review.

Thanks to Hao Jin and Sheng Zha, who have prepared the docs of development
guide and list for NumPy operators, we would like to share them in the
public space and call for contributions on reviewing NumPy operator PRs and
implementing the remaining operators in the list.

Thank you for your contribution on bringing NumPy-like coding experience
into MXNet and efforts on transforming MXNet into a super user-friendly
framework.

Best regards,
Jun

References
[1] NumPy Operator Development Guide:
https://cwiki.apache.org/confluence/display/MXNET/How+to+Implement+a+NumPy-Compatible+Operator+in+MXNet
[2] NumPy Operator Coverage List:
https://cwiki.apache.org/confluence/display/MXNET/NumPy+Operator+Coverage+Status
[3] NumPy Operators in Code Review:
https://github.com/apache/incubator-mxnet/pulls?q=is%3Apr+is%3Aopen+label%3ANumpy
[4] How to implement an operator in MXNet:
https://mxnet.incubator.apache.org/versions/master/faq/add_op_in_backend.html