Re: [RESULT][LAZY VOTE] Next MXNet release

[Sheng Zha]

Reporting back on this thread, I received feedbacks with some valid
concerns:
- There are different parties that are already working toward the
previously communicated timeline.
- It creates a hassle for people.

Although I'd love to see the release happening soon, let's keep the
existing timeline. Next time when a release happens, we can consider
releasing multiple versions at the same time with more thought and
coordination.

-sz

On Wed, Nov 7, 2018 at 8:50 AM kellen sunderland <
kellen.sunderl...@gmail.com> wrote:

> +1 to trying to get a 1.4.0 Nov release.  I think the MKLDNN work alone is
> a headline feature that users would love to get their hands on.
>
> On Tue, Nov 6, 2018 at 11:32 PM Sheng Zha  wrote:
>
> > I'd like to propose that we expedite the 1.4.0 release slightly as there
> > doesn't seem to be a rule that prevents a minor release from happening at
> > the same time of a patch release. This would shorten the time it takes
> for
> > new features to reach users. Proposed revision to the timeline:
> > - Code freeze: 11/9
> > - Release published: 11/22
> >
> > If there's no issue about both the proposal and new timeline, I'd be
> happy
> > to manage 1.4.0 release as release manager.
> >
> > -sz
> >
> > On Thu, Nov 1, 2018 at 7:56 AM Steffen Rochel 
> > wrote:
> >
> > > There have been no objections, so lazy vote passed.
> > > Anton volunteered to manage the 1.3.1 release and Naveen will support
> him
> > > as co-manager to handle the release tasks requiring committer powers.
> > > Please support Anton for a smooth 1.3.1 release process.
> > >
> > > I'm still looking for volunteers to manage / co-manage the 1.4.0
> release.
> > >
> > > Regards,
> > > Steffen
> > >
> > > On Sun, Oct 28, 2018 at 7:33 PM Steffen Rochel <
> steffenroc...@gmail.com>
> > > wrote:
> > >
> > > > I calling a lazy vote to release MXNet
> > > > 1.3.1 (patch release) and 1.4.0 (minor relase).
> > > >
> > > > Release content: release proposal page
> > > > <
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
> > > >
> > > >
> > > > Target milestones:
> > > > *1.3.1*
> > > >
> > > >- Code Freeze: 10/31
> > > >- Release published: 11/13
> > > >
> > > > *1.4.0:*
> > > >
> > > >- Code Freeze: 11/13
> > > >- Release published: 12/13 (if possible announce during NIPS)
> > > >
> > > >
> > > > The vote will be open until Wednesday October 31, 2018 8.00pm PDT.
> > > >
> > > > Regards,
> > > > Steffen
> > > >
> > > > On Fri, Oct 26, 2018 at 7:56 AM Steffen Rochel <
> > steffenroc...@gmail.com>
> > > > wrote:
> > > >
> > > >> During the Hangout on Wednesday multiple release proposals have been
> > > >> discussed. I summarized discussion here
> > > >> <
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Hangout+October+24th+2018+8am+and+5pm+PDT
> > >
> > > and
> > > >> updated the release proposal page
> > > >> <
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
> > > >
> > > >> .
> > > >> Please review, provide feedback and propose changes.
> > > >> I plan to start a lazy vote on Sunday regarding the release
> proposal.
> > > >>
> > > >> Calling for volunteers to manage the 1.3.1 and 1.4.0 release.
> > > >>
> > > >> Regards,
> > > >> Steffen
> > > >>
> > > >> On Tue, Oct 9, 2018 at 7:20 AM kellen sunderland <
> > > >> kellen.sunderl...@gmail.com> wrote:
> > > >>
> > > >>> Hey Steffen,
> > > >>>
> > > >>> Recommend these be merged into patch release:
> > > >>>
> > > >>> https://github.com/apache/incubator-mxnet/pull/12631
> > > >>> https://github.com/apache/incubator-mxnet/pull/12603
> > > >>> https://github.com/apache/incubator-mxnet/pull/12499
> > > >>>
> > > >>> -Kellen
> > > >>>
> > > >>> On Tue, Oct 2, 2018 at 7:17 AM Zhao, Patric  >
> > > >>> wrote:
> > > >>>
> > > >>> > Thanks to let us know this discussion.
> > > >>> > Because we don't have enough bandwidth to track the different
> > > sources,
> > > >>> > like discussion forum.
> > > >>> >
> > > >>> > I think the best way is to open issue in the github so that we
> can
> > > >>> > answer/solve the issue in time :)
> > > >>> >
> > > >>> > Thanks,
> > > >>> >
> > > >>> > --Patric
> > > >>> >
> > > >>> > > -Original Message-
> > > >>> > > From: Afrooze, Sina [mailto:sina@gmail.com]
> > > >>> > > Sent: Tuesday, October 2, 2018 1:14 AM
> > > >>> > > To: dev@mxnet.incubator.apache.org
> > > >>> > > Cc: Ye, Jason Y ; Zai, Alexander
> > > >>> > > ; Zheng, Da 
> > > >>> > > Subject: Re: [Discuss] Next MXNet release
> > > >>> > >
> > > >>> > > This post suggests there is a regression from 1.1.0 to 1.2.1
> > > related
> > > >>> to
> > > >>> > > MKLDNN integration:
> > > >>> https://discuss.mxnet.io/t/mxnet-1-2-1-module-get-
> > > >>> > > outputs/1882
> > > >>> > >
> > > >>> > > The error is related to MKLDNN layout not being converted back
> to
> > > >>> MXNet
> > > >>> > > layout in some operator: " !IsMKLDNNData() We can’t generate
> > TBlob
> 

Re: [Mentor needed] Create ticket to add webhook for the new label bot

[Marco de Abreu]

Thanks Sebastian for creating the ticket. The webhook has successfully been
created. During our production tests, we have encountered some issues which
will delay the release by a bit. From that point, we don't need further
support from Infra and we're able to make the changes on our side.

Best regards,
Marco

On Wed, Nov 7, 2018 at 5:02 PM Marco de Abreu 
wrote:

> Hello,
>
> the new label bot [1] is in the final stage of deployment. We would now
> need the assistance from Apache Infra to install a GitHub webhook. Mentors,
> would you mind helping us to create a JIRA ticket with Infra? The content
> would be as follows:
>
> Hello Apache Infra,
>
> Apache MXNet (incubating) would like to request a new GitHub webhook. The
> discussion is available at
> https://lists.apache.org/thread.html/273229e7b9f28af5a198011863e5b16da7c7091aac8350dc0bd3a60e@%3Cdev.mxnet.apache.org%3E.
> The details are as follows:
>
> - Endpoint: labelbot-webhook.mxnet-ci-dev.amazon-ml.com/dev/send_to_sqs
> - Content type: application/json
> - Secure hash: Will be provided by Marco de Abreu
> - SSL verification: Enabled
> - Triggered events: Issue comments, Issues, Labels, pull requests, pull
> request reviews, pull request review comments
> - Enable "We will deliver event details when this hook is triggered"
>
> An example config is available at https://imgur.com/a/i74szvB.
>
>
> Marco de Abreu will join the HipChat channel to assist from the project
> side.
>
> Thank you,
> %MENTOR_NAME%
>
>
> Thanks for your support!
>
> Best regards,
> Marco
>
> [1]:
> https://lists.apache.org/thread.html/273229e7b9f28af5a198011863e5b16da7c7091aac8350dc0bd3a60e@%3Cdev.mxnet.apache.org%3E
>

Requesting access for SLACK

[Gaurav Gireesh]

Hi!
I would like to request access to the Slack channel for MXNet.

Thanks and regards,
Gaurav Gireesh

Re: Requesting Access for SLACK

[Steffen Rochel]

Welcome Gavin, added you to slack.
Steffen

On Tue, Nov 6, 2018 at 6:52 AM Gavin M. Bell 
wrote:

> Hello,
>
> I would like to please have access to slack for MXNet.
>
> --
> Sincerely,
> Gavin M. Bell
>
>  "Never mistake a clear view for a short distance."
>   -Paul Saffo
>

Re: Requesting slack access

[Steffen Rochel]

Hi Kamaci - welcome to Apache MXNet project. Please let us know what you
working on and reach out if you need help.
Steffen

On Wed, Nov 7, 2018 at 12:01 AM Furkan KAMACI 
wrote:

> Hi,
>
> I would like to access to Slack.
>
> Kind Regards,
> Furkan KAMACI
>

Re: [RESULT][LAZY VOTE] Next MXNet release

[kellen sunderland]

+1 to trying to get a 1.4.0 Nov release.  I think the MKLDNN work alone is
a headline feature that users would love to get their hands on.

On Tue, Nov 6, 2018 at 11:32 PM Sheng Zha  wrote:

> I'd like to propose that we expedite the 1.4.0 release slightly as there
> doesn't seem to be a rule that prevents a minor release from happening at
> the same time of a patch release. This would shorten the time it takes for
> new features to reach users. Proposed revision to the timeline:
> - Code freeze: 11/9
> - Release published: 11/22
>
> If there's no issue about both the proposal and new timeline, I'd be happy
> to manage 1.4.0 release as release manager.
>
> -sz
>
> On Thu, Nov 1, 2018 at 7:56 AM Steffen Rochel 
> wrote:
>
> > There have been no objections, so lazy vote passed.
> > Anton volunteered to manage the 1.3.1 release and Naveen will support him
> > as co-manager to handle the release tasks requiring committer powers.
> > Please support Anton for a smooth 1.3.1 release process.
> >
> > I'm still looking for volunteers to manage / co-manage the 1.4.0 release.
> >
> > Regards,
> > Steffen
> >
> > On Sun, Oct 28, 2018 at 7:33 PM Steffen Rochel 
> > wrote:
> >
> > > I calling a lazy vote to release MXNet
> > > 1.3.1 (patch release) and 1.4.0 (minor relase).
> > >
> > > Release content: release proposal page
> > > <
> >
> https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
> > >
> > >
> > > Target milestones:
> > > *1.3.1*
> > >
> > >- Code Freeze: 10/31
> > >- Release published: 11/13
> > >
> > > *1.4.0:*
> > >
> > >- Code Freeze: 11/13
> > >- Release published: 12/13 (if possible announce during NIPS)
> > >
> > >
> > > The vote will be open until Wednesday October 31, 2018 8.00pm PDT.
> > >
> > > Regards,
> > > Steffen
> > >
> > > On Fri, Oct 26, 2018 at 7:56 AM Steffen Rochel <
> steffenroc...@gmail.com>
> > > wrote:
> > >
> > >> During the Hangout on Wednesday multiple release proposals have been
> > >> discussed. I summarized discussion here
> > >> <
> >
> https://cwiki.apache.org/confluence/display/MXNET/Hangout+October+24th+2018+8am+and+5pm+PDT
> >
> > and
> > >> updated the release proposal page
> > >> <
> >
> https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
> > >
> > >> .
> > >> Please review, provide feedback and propose changes.
> > >> I plan to start a lazy vote on Sunday regarding the release proposal.
> > >>
> > >> Calling for volunteers to manage the 1.3.1 and 1.4.0 release.
> > >>
> > >> Regards,
> > >> Steffen
> > >>
> > >> On Tue, Oct 9, 2018 at 7:20 AM kellen sunderland <
> > >> kellen.sunderl...@gmail.com> wrote:
> > >>
> > >>> Hey Steffen,
> > >>>
> > >>> Recommend these be merged into patch release:
> > >>>
> > >>> https://github.com/apache/incubator-mxnet/pull/12631
> > >>> https://github.com/apache/incubator-mxnet/pull/12603
> > >>> https://github.com/apache/incubator-mxnet/pull/12499
> > >>>
> > >>> -Kellen
> > >>>
> > >>> On Tue, Oct 2, 2018 at 7:17 AM Zhao, Patric 
> > >>> wrote:
> > >>>
> > >>> > Thanks to let us know this discussion.
> > >>> > Because we don't have enough bandwidth to track the different
> > sources,
> > >>> > like discussion forum.
> > >>> >
> > >>> > I think the best way is to open issue in the github so that we can
> > >>> > answer/solve the issue in time :)
> > >>> >
> > >>> > Thanks,
> > >>> >
> > >>> > --Patric
> > >>> >
> > >>> > > -Original Message-
> > >>> > > From: Afrooze, Sina [mailto:sina@gmail.com]
> > >>> > > Sent: Tuesday, October 2, 2018 1:14 AM
> > >>> > > To: dev@mxnet.incubator.apache.org
> > >>> > > Cc: Ye, Jason Y ; Zai, Alexander
> > >>> > > ; Zheng, Da 
> > >>> > > Subject: Re: [Discuss] Next MXNet release
> > >>> > >
> > >>> > > This post suggests there is a regression from 1.1.0 to 1.2.1
> > related
> > >>> to
> > >>> > > MKLDNN integration:
> > >>> https://discuss.mxnet.io/t/mxnet-1-2-1-module-get-
> > >>> > > outputs/1882
> > >>> > >
> > >>> > > The error is related to MKLDNN layout not being converted back to
> > >>> MXNet
> > >>> > > layout in some operator: " !IsMKLDNNData() We can’t generate
> TBlob
> > >>> for
> > >>> > > MKLDNN data. Please use Reorder2Default() to generate a new
> NDArray
> > >>> > > first"
> > >>> > >
> > >>> > > Sina
> > >>> > >
> > >>> > >
> > >>> > >
> > >>> > >
> > >>> > > On 9/30/18, 6:55 PM, "Steffen Rochel" 
> > >>> wrote:
> > >>> > >
> > >>> > > Thanks Patrick.
> > >>> > > Updated roadmap and next release content.
> > >>> > >
> > >>> > > Patrick - suggest to send a reminder to review the design doc
> > and
> > >>> > collect
> > >>> > > feedback.
> > >>> > > Are there still known issues or gaps before we declare
> MKL-DNN
> > >>> > > integration
> > >>> > > as GA?
> > >>> > >
> > >>> > > Regards,
> > >>> > > Steffen
> > >>> > >
> > >>> > > On Sat, Sep 29, 2018 at 1:31 AM Zhao, Patric <
> > >>> patric.z...@intel.com>
> > >>> > > wrote:
> > >>> > >
> > >>> > 

Re: [Announce] Upcoming Apache MXNet (incubating) 1.3.1 patch release

[Anton Chernov]

Yes, you are right about the versions wording, thanks for clarification.

A performance improvement can be considered a bugfix as well. I see no big
risks in including PR's by Haibin and Lin into the patch release.

@Haibin, if you can reopen the PR's they should be good to go for the
relase, considering the importance of the improvements.

I propose the following bugfixes for the release as well (already created
corresponding PR's):

Fixed __setattr__ method of _MXClassPropertyMetaClass (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13157

fixed symbols naming in RNNCell, LSTMCell, GRUCell (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13158

We will be starting to merge the PR's shortly. If are no more proposals for
backporting I would consider the list as set.

Best
Anton

ср, 7 нояб. 2018 г. в 17:01, Sheng Zha :

> Hi Anton,
>
> I hear your concern about a simultaneous 1.4.0 release and it certainly is
> a valid one.
>
> Regarding the release, let’s agree on the language first. According to
> semver.org, 1.3.1 release is considered patch release, which is for
> backward compatible bug fixes, while 1.4.0 release is considered minor
> release, which is for backward compatible new features. A major release
> would mean 2.0.
>
> The three PRs suggested by Haibin and Lin are all introducing new
> features. If they go into a patch release, it would require an exception
> accepted by the community. Also, if other violation happens it could be
> ground for declining a release during votes.
>
> -sz
>
> > On Nov 7, 2018, at 2:25 AM, Anton Chernov  wrote:
> >
> > [MXNET-1179] Enforce deterministic algorithms in convolution layers
>

[Mentor needed] Create ticket to add webhook for the new label bot

[Marco de Abreu]

Hello,

the new label bot [1] is in the final stage of deployment. We would now
need the assistance from Apache Infra to install a GitHub webhook. Mentors,
would you mind helping us to create a JIRA ticket with Infra? The content
would be as follows:

Hello Apache Infra,

Apache MXNet (incubating) would like to request a new GitHub webhook. The
discussion is available at
https://lists.apache.org/thread.html/273229e7b9f28af5a198011863e5b16da7c7091aac8350dc0bd3a60e@%3Cdev.mxnet.apache.org%3E.
The details are as follows:

- Endpoint: labelbot-webhook.mxnet-ci-dev.amazon-ml.com/dev/send_to_sqs
- Content type: application/json
- Secure hash: Will be provided by Marco de Abreu
- SSL verification: Enabled
- Triggered events: Issue comments, Issues, Labels, pull requests, pull
request reviews, pull request review comments
- Enable "We will deliver event details when this hook is triggered"

An example config is available at https://imgur.com/a/i74szvB.


Marco de Abreu will join the HipChat channel to assist from the project
side.

Thank you,
%MENTOR_NAME%


Thanks for your support!

Best regards,
Marco

[1]:
https://lists.apache.org/thread.html/273229e7b9f28af5a198011863e5b16da7c7091aac8350dc0bd3a60e@%3Cdev.mxnet.apache.org%3E

Re: CLion dev setup tutorial

[Marco de Abreu]

Great detailed guide, thanks Jose! I'm sure it will be of great use for
many developers.

-Marco

Am Mi., 7. Nov. 2018, 15:18 hat Jose Luis Contreras Santos <
joseluis.contreras.san...@gmail.com> geschrieben:

> Hi all,
>
> I recently published a guide on how to setup CLion for MXNet development on
> Mac. It's published on Confluence here
> <
> https://cwiki.apache.org/confluence/display/MXNET/CLion+setup+for+MXNet+development+on+Mac
> >,
> so if you are interested have a look at it and let me know if there's
> anything which could be improved.
>
> For non Mac users, there's also a section in the end about remote host
> development. With this  new feature of the upcoming version of CLion, you
> can work on a remote Linux machine using your local IDE.
>
> Thanks,
>
> Jose
>

Unit test breakdown by time

[Pedro Larroy]

Hi

I made a quick breakdown of time spent on unit tests (in seconds) per test
and per test class. I run CPU tests on an m1 instance.

As you can see the slowest test classes are:

test_operator, 630.92699
test_gluon, 261.106017
test_profiler, 159.427002
test_gluon_model_zoo, 130.854
test_metric_perf, 88.016
test_gluon_data, 59.193
test_io, 58.9280004
test_optimizer, 54.630999

I think we should dive deep in some of those tests and see how can we make
them lighter.  Any thoughts?

Pedro.
test_operator, 630.92699
test_gluon, 261.106017
test_profiler, 159.427002
test_gluon_model_zoo, 130.854
test_metric_perf, 88.016
test_gluon_data, 59.193
test_io, 58.9280004
test_optimizer, 54.630999
test_loss, 38.6230005
test_contrib_control_flow, 31.102
test_sparse_operator, 28.695
test_image.TestImage, 24.4339997
test_recordio, 24.0059997
test_ndarray, 14.8279994
test_sparse_ndarray, 12.546
test_module, 8.017
test_gluon_contrib, 6.757
test_contrib_io, 3.525
test_gluon_rnn, 2.838
test_subgraph, 2.56
test_executor, 1.762
test_gluon_utils, 1.462
test_contrib_text, 1.032
test_kvstore, 0.942
test_symbol, 0.397
test_subgraph_op, 0.345
test_gluon_trainer, 0.27
test_test_utils, 0.251
test_contrib_optimizer, 0.235
test_rnn, 0.16504
test_autograd, 0.15305
test_contrib_operator, 0.14202
test_gluon_data_vision, 0.077
test_exc_handling, 0.063
test_metric, 0.043003
test_contrib_autograd, 0.039
test_init, 0.027997
test_contrib_svrg_module, 0.025
test_thread_local, 0.023
test_predictor, 0.02
test_multi_device_exec, 0.016
test_contrib_svrg_optimizer, 0.013001
test_engine, 0.012
test_infer_type, 0.012
test_infer_shape, 0.009001
test_model_parallel, 0.009
test_contrib_krprod, 0.008
test_viz, 0.006
test_attr, 0.005
test_engine_import, 0.002
test_base.MXNetDataDirTest, 0.0
nose.failure.Failure, 0.0
test_models, 130.854
test_slice_pooling2d_slice_pooling2d, 126.273
test_psroipooling, 101.859
test_pick, 99.113
test_continuous_profile_and_instant_marker, 88.328
test_metric_performance, 88.016
test_broadcast_binary_op, 87.497
test_datasets, 45.359
test_layer_norm, 42.679
test_order, 36.46
test_NDArrayIter, 32.427
test_slice_pooling2d, 29.235
test_slice_batchnorm, 28.137
test_stack, 26.771
test_slice_batchnorm_reshape_batchnorm, 25.103
test_profiler, 24.563
test_recordio_pack_label, 23.987
test_lstm_dropout, 23.58
test_adam, 23.38
test_reduce, 19.459
test_Cifar10Rec, 18.818
test_cond, 17.734
test_gru_dropout, 17.297
test_lstm_bidirectional, 16.692
test_imageiter, 16.551
test_profile_tune_pause_resume, 14.664
test_legacy_save_params, 14.139
test_gru_bidirectional, 13.197
test_laop_2, 11.906
test_lstm_sym, 10.996
test_correlation, 10.212
test_rms, 10.177
test_profile_counter, 9.983
test_symbol_block, 9.779
test_while_loop_for_foreach, 9.172
test_gru_sym, 8.293
test_conv2d_16c, 8.189
test_one_hot, 7.545
test_order, 7.424
test_profile_event, 7.347
test_profile_task, 7.298
test_synthetic_dataset_generator, 7.261
test_profile_frame, 7.226
test_laop_3, 6.976
test_binary_op, 6.563
test_elemwise_binary_ops, 6.522
test_rnnrelu_dropout, 6.42
test_datasets, 6.382
test_rnntanh_dropout, 6.345
test_multi_worker, 6.325
test_pad, 6.01
test_multi_proposal_op, 5.72
test_sparse_square_sum, 5.702
test_executor_group, 5.57
test_hybrid_static_memory, 5.43
test_MNISTIter, 5.16
test_recordimage_dataset_with_data_loader_multiworker, 4.896
test_nadam, 4.88
test_cast_storage_ex, 4.652
test_sparse_nd_broadcast, 4.591
test_batchnorm_training, 4.399
test_l2_normalization, 4.297
test_sgd, 4.192
test_poisson_nllloss_mod, 4.033
test_triplet_loss, 3.862
test_ctc_loss_train, 3.825
test_resize_short, 3.794
test_rnntanh_bidirectional, 3.721
test_unary_math_operators, 3.666
test_contrib_DataLoaderIter, 3.525
test_huber_loss, 3.433
test_crop, 3.402
test_saveload, 3.36
test_squared_hinge_loss, 3.289
test_sparse_dot, 3.25
test_signum, 3.184
test_hinge_loss, 3.138
test_diag, 3.049
test_roipooling, 3.038
test_sparse_sgd, 2.919
test_rnntanh_sym, 2.816
test_sparse_storage_fallback, 2.771
test_dtype, 2.719
test_hybrid_static_memory_switching, 2.704
test_batch_dot, 2.601
test_make_subgraph, 2.56
test_sample_weight_loss, 2.558
test_batchnorm_fallback, 2.513
test_where, 2.459
test_ftml, 2.37
test_l2_loss, 2.303
test_l1_loss, 2.296
test_dot, 2.262
test_ce_loss, 2.218
test_laop, 2.174
test_LibSVMIter, 2.13
test_bce_loss, 2.128
test_kl_loss, 2.127
test_nag, 2.023
test_broadcast, 2.019
test_ndarray_indexing, 1.945
test_sparse_retain, 1.838
test_op_roi_align, 1.797
test_factorization_machine_module, 1.577
test_bind, 1.56
test_stn, 1.486
test_multiprocessing_download_successful, 1.457
test_concat, 1.378
test_quadratic_function, 1.361
test_while_loop_simple_forward, 1.357
test_broadcast, 1.343
test_spacetodepth, 1.288
test_recordimage_dataset, 1.261
test_while_loop_rnn, 1.238
test_broadcast_binary, 1.196

CLion dev setup tutorial

[Jose Luis Contreras Santos]

Hi all,

I recently published a guide on how to setup CLion for MXNet development on
Mac. It's published on Confluence here
,
so if you are interested have a look at it and let me know if there's
anything which could be improved.

For non Mac users, there's also a section in the end about remote host
development. With this  new feature of the upcoming version of CLion, you
can work on a remote Linux machine using your local IDE.

Thanks,

Jose

Re: [Announce] Upcoming Apache MXNet (incubating) 1.3.1 patch release

[Anton Chernov]

@Sheng: Sorry, nevermind. It was already suggested by Lin.

The following backport PR's have been created:

allow foreach on input with 0 length (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13151

[MXNET-1179] Enforce deterministic algorithms in convolution layers (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13152

Document the newly added env variable (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13156

add/update infer_range docs (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13153

fix broken Python IO API docs (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13154

fix broken links (v1.3.x)
https://github.com/apache/incubator-mxnet/pull/13155


Best
Anton


ср, 7 нояб. 2018 г. в 10:49, Anton Chernov :

> Hi Sheng,
>
> thanks for you suggestions. Personally, I would not rush with new major
> release as this breaks the pace and creates unnecessary pressure in my
> opinion.
>
> If the changes suggested by Haibin are really important then I think we
> can consider them for the minor release, even if they are not strictly
> speaking *bugfixes*. Do you think that might be an option?
>
> And did I understand correctly, you are suggesting:
>
> [MXNET-1179] Enforce deterministic algorithms in convolution layers
> https://github.com/apache/incubator-mxnet/pull/12992
>
> for the 1.3.1 release?
>
> Best
> Anton
>
>
> ср, 7 нояб. 2018 г. в 0:59, Sheng Zha :
>
>> Similar to the two PRs that Haibin suggested, 12992 introduces new
>> interface for controlling determinism, which is better suited for minor
>> release.
>>
>> I think other than lack of release manager to drive 1.4.0 release,
>> there’s no reason we cannot do two releases (1.4.0 & 1.3.1) at the same
>> time. I’m willing to help with the 1.4.0 release to make these new features
>> available one month sooner, if there’s no other concern.
>>
>> -sz
>>
>> > On Nov 6, 2018, at 3:30 PM, Lin Yuan  wrote:
>> >
>> > Hi Anton,
>> >
>> > Thanks for helping the release.
>> > The following PRs are needed by customers who want to use deterministic
>> > CUDNN convolution algorithms:
>> >
>> > https://github.com/apache/incubator-mxnet/pull/12992
>> > https://github.com/apache/incubator-mxnet/pull/13049
>> >
>> > Thanks！
>> >
>> > Lin
>> >
>> >
>> > On Tue, Nov 6, 2018 at 1:51 PM Aaron Markham > >
>> > wrote:
>> >
>> >> Hi Anton,
>> >> I have the following suggestions for fixes to include in 1.3.1. These
>> each
>> >> have updates to files that will impact docs generation for the 1.3.x
>> >> version of the website's Python API docs:
>> >>
>> >> https://github.com/apache/incubator-mxnet/pull/12879
>> >> https://github.com/apache/incubator-mxnet/pull/12871
>> >> https://github.com/apache/incubator-mxnet/pull/12856
>> >>
>> >> Thanks,
>> >> Aaron
>> >>
>> >>> On Tue, Nov 6, 2018 at 1:29 PM Lai Wei  wrote:
>> >>>
>> >>> Hi Anton,
>> >>>
>> >>> Thanks for driving this, I would like to include the following fix in
>> >>> 1.3.1:
>> >>> Allow infer shape partial on foreach operator:
>> >>> https://github.com/apache/incubator-mxnet/pull/12471
>> >>>
>> >>> Keras-MXNet needs this functionality to infer shape partially
>> >>> on foreach operator. (Used in RNN operators)
>> >>>
>> >>> Thanks a lot!
>> >>>
>> >>>
>> >>> Best Regards
>> >>> Lai Wei
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Nov 6, 2018 at 10:44 AM Haibin Lin 
>> >>> wrote:
>> >>>
>>  Hi Naveen and Anton,
>> 
>>  Thanks for pointing that out. You are right that these are not
>> critical
>>  fixes. Putting them in 1.4.0 is more appropriate. PRs are closed.
>> 
>>  Best,
>>  Haibin
>> 
>>  On Tue, Nov 6, 2018 at 7:35 AM Naveen Swamy 
>> >> wrote:
>> 
>> > Please note that this is a patch release(1.3.1) to address critical
>>  bugs!,
>> > For everything else please wait for 1.4.0 which is planned very
>> >> shortly
>> > after 1.3.1
>> >
>> >> On Nov 6, 2018, at 7:17 AM, Anton Chernov 
>> >>> wrote:
>> >>
>> >> The following PR's have been created so far:
>> >>
>> >> Infer dtype in SymbolBlock import from input symbol (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13117
>> >>
>> >> [MXNET-953] Fix oob memory read (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13118
>> >>
>> >> [MXNET-969] Fix buffer overflow in RNNOp (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13119
>> >>
>> >> [MXNET-922] Fix memleak in profiler (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13120
>> >>
>> >> Set correct update on kvstore flag in dist_device_sync mode
>> >> (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13121
>> >>
>> >> update mshadow (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13122
>> >>
>> >> CudnnFind() usage improvements (v1.3.x)
>> >> https://github.com/apache/incubator-mxnet/pull/13123
>> >>
>> >> Fix lazy record io when used with 

Re: [Announce] Upcoming Apache MXNet (incubating) 1.3.1 patch release

[Anton Chernov]

Hi Sheng,

thanks for you suggestions. Personally, I would not rush with new major
release as this breaks the pace and creates unnecessary pressure in my
opinion.

If the changes suggested by Haibin are really important then I think we can
consider them for the minor release, even if they are not strictly speaking
*bugfixes*. Do you think that might be an option?

And did I understand correctly, you are suggesting:

[MXNET-1179] Enforce deterministic algorithms in convolution layers
https://github.com/apache/incubator-mxnet/pull/12992

for the 1.3.1 release?

Best
Anton


ср, 7 нояб. 2018 г. в 0:59, Sheng Zha :

> Similar to the two PRs that Haibin suggested, 12992 introduces new
> interface for controlling determinism, which is better suited for minor
> release.
>
> I think other than lack of release manager to drive 1.4.0 release, there’s
> no reason we cannot do two releases (1.4.0 & 1.3.1) at the same time. I’m
> willing to help with the 1.4.0 release to make these new features available
> one month sooner, if there’s no other concern.
>
> -sz
>
> > On Nov 6, 2018, at 3:30 PM, Lin Yuan  wrote:
> >
> > Hi Anton,
> >
> > Thanks for helping the release.
> > The following PRs are needed by customers who want to use deterministic
> > CUDNN convolution algorithms:
> >
> > https://github.com/apache/incubator-mxnet/pull/12992
> > https://github.com/apache/incubator-mxnet/pull/13049
> >
> > Thanks！
> >
> > Lin
> >
> >
> > On Tue, Nov 6, 2018 at 1:51 PM Aaron Markham 
> > wrote:
> >
> >> Hi Anton,
> >> I have the following suggestions for fixes to include in 1.3.1. These
> each
> >> have updates to files that will impact docs generation for the 1.3.x
> >> version of the website's Python API docs:
> >>
> >> https://github.com/apache/incubator-mxnet/pull/12879
> >> https://github.com/apache/incubator-mxnet/pull/12871
> >> https://github.com/apache/incubator-mxnet/pull/12856
> >>
> >> Thanks,
> >> Aaron
> >>
> >>> On Tue, Nov 6, 2018 at 1:29 PM Lai Wei  wrote:
> >>>
> >>> Hi Anton,
> >>>
> >>> Thanks for driving this, I would like to include the following fix in
> >>> 1.3.1:
> >>> Allow infer shape partial on foreach operator:
> >>> https://github.com/apache/incubator-mxnet/pull/12471
> >>>
> >>> Keras-MXNet needs this functionality to infer shape partially
> >>> on foreach operator. (Used in RNN operators)
> >>>
> >>> Thanks a lot!
> >>>
> >>>
> >>> Best Regards
> >>> Lai Wei
> >>>
> >>>
> >>>
> >>> On Tue, Nov 6, 2018 at 10:44 AM Haibin Lin 
> >>> wrote:
> >>>
>  Hi Naveen and Anton,
> 
>  Thanks for pointing that out. You are right that these are not
> critical
>  fixes. Putting them in 1.4.0 is more appropriate. PRs are closed.
> 
>  Best,
>  Haibin
> 
>  On Tue, Nov 6, 2018 at 7:35 AM Naveen Swamy 
> >> wrote:
> 
> > Please note that this is a patch release(1.3.1) to address critical
>  bugs!,
> > For everything else please wait for 1.4.0 which is planned very
> >> shortly
> > after 1.3.1
> >
> >> On Nov 6, 2018, at 7:17 AM, Anton Chernov 
> >>> wrote:
> >>
> >> The following PR's have been created so far:
> >>
> >> Infer dtype in SymbolBlock import from input symbol (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13117
> >>
> >> [MXNET-953] Fix oob memory read (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13118
> >>
> >> [MXNET-969] Fix buffer overflow in RNNOp (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13119
> >>
> >> [MXNET-922] Fix memleak in profiler (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13120
> >>
> >> Set correct update on kvstore flag in dist_device_sync mode
> >> (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13121
> >>
> >> update mshadow (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13122
> >>
> >> CudnnFind() usage improvements (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13123
> >>
> >> Fix lazy record io when used with dataloader and multi_worker > 0
> > (v1.3.x)
> >> https://github.com/apache/incubator-mxnet/pull/13124
> >>
> >>
> >> As stated previously I would be rather opposed to have following
> >> PR's
>  it
> > in
> >> the patch release:
> >>
> >> Gluon LSTM Projection and Clipping Support (#13055) v1.3.x
> >> https://github.com/apache/incubator-mxnet/pull/13129
> >>
> >> sample_like operators (#13034) v1.3.x
> >> https://github.com/apache/incubator-mxnet/pull/13130
> >>
> >>
> >> Best
> >> Anton
> >>
> >> вт, 6 нояб. 2018 г. в 16:06, Anton Chernov :
> >>
> >>> Hi Haibin,
> >>>
> >>> I have a few comments regarding the proposed performance
> >> improvement
> >>> changes.
> >>>
> >>> CUDNN support for LSTM with projection & clipping
> >>> https://github.com/apache/incubator-mxnet/pull/13056
> >>>
> 

Re: [DISCUSS] Speedup non-code PR in CI

[Anton Chernov]

Hi Lin,

thanks for your suggestion. I think it makes total sense. The triggering
logic of the verification build is in the Jenkinsfile [1]. We would be
happy if you could drive this and introduce a PR that implements this check.

Best
Anton

[1] https://github.com/apache/incubator-mxnet/blob/master/Jenkinsfile

вт, 6 нояб. 2018 г. в 20:55, Lin Yuan :

> Kellen and Pedro,
>
> Thanks for your pointers. I am not an expert in CI but one naive speedup I
> can see is that if the PR only contains *.md file, then skip the build and
> testing cycles. This can make documentation/correction easier and save
> computation resource for other needed tests. Any side effect there?
>
> Thanks,
>
> Lin
>

Requesting slack access

[Furkan KAMACI]

Hi,

I would like to access to Slack.

Kind Regards,
Furkan KAMACI