-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[Discussion] 1.5.1 Patch Release #15613
Comments
Reports of inference errors on 1.5.0: |
Possible issue with asnumpy(), but not able to reproduce yet #15431 |
license issues need to be fixed before next release #15542 |
FYI #15281 (comment) is fixed in 1.5.0 |
FYI #15337 is also resolved |
@mxnet-label-bot add [discussion] |
I will track Julia stuffs that need to be backported here: |
Hi, I just created a label "Backport 1.5" (https://github.com/apache/incubator-mxnet/labels/Backport%201.5). |
I'd prefer if we use multiple PRs which only contain cherry-picks from master. That way, we don't squash and keep the references. |
ah, okay |
@samskalicky thanks for starting the discussion. @PatricZhao @TaoLv could you drive this release? |
It's great to lead the release. @TaoLv @juliusshufan will be working on this. |
Update: moved this to 1.6.0 scopenightly test failure need to be fixed: |
Thanks for reporting. Added it to https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status |
Hi, I’m fixing the bug of two C APIs It will be finished this week. |
Thanks for proposing, @wkcn . |
@TaoLv Yes, it is a bug in 1.5.0 release https://github.com/apache/incubator-mxnet/blob/v1.5.x/src/c_api/c_api.cc#L1537 It need to be fixed, otherwise users couldn't use these two C APIs in the release version of MXNet. |
I mean does it also exist in v1.4.x releases? |
@TaoLv It doesn't exist in v1.4.x release. The bug was introdueced firstly in v1.5.x release. |
Thanks for the clarification. Do you have a github issue for that? I add it to the track list. |
@wkcn, thanks for your report and contribution! The issue and your fix are added to https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status. |
What's the issue with MShadow? Did they have to do a force push / history re-write again? We may indeed have to backport that to other release branches. |
@KellenSunderland mshadow source code is donated and merged to MXNet. See #15600 and dmlc/mshadow#373. So it's not a git submodule any more. |
For the source downloaded before mshadow merged into MXNet, users need to remove |
@wkcn that doesnt work for me:
|
Hi @samskalicky , I can download |
@KellenSunderland Could you please include the TensorRT patches you just mentioned into the cwiki? https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status Thanks for your support! |
Thank you @KellenSunderland . I just included these patches to the table on cwiki. Please help take a look: https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status |
No problem Tao, I can probably cherry-pick them a bit later today. |
Benchmark doc fix PR #15769 |
This PR fixes a memory misalignment bug in topk operator introduced recently. Please add it to 1.5.1 patch release: Thanks |
@KellenSunderland, the 3 PRs were already merged to v1.5.x. Please update for the other two if we still need them. |
@ChaiBapchya, thank you for the report. Could you please cherry pick it to the v1.5.x branch and tag me in the PR? |
@samskalicky , please pick them to v1.5.x and tag me in the PR. I will update the cwiki page accordingly. |
@apeforest Any update? Is it still true that we can pick this to v1.5.x? |
No, please create pull requests instead |
Haven't we already passed code freeze?
…On Tue, Sep 10, 2019 at 11:16 PM Marco de Abreu ***@***.***> wrote:
No, please create pull requests instead
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15613>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABT54SKA7OO3WMTGBRTZXTTQJCEMVANCNFSM4IFKN5YA>
.
|
Yes, we have passed code freeze and the rc0 was already tagged. Front-end packaging is in progress. One can still commit code change to the v1.5.x branch but that will be not included in the vote for rc0. |
|
Any news on 1.5.1? |
Let's start a discussion here about the known issues with 1.5.0 to put into a patch release.
Create (or locate existing) issue/pull request for the item, note the issue/pull request number.
Comment in this issue: 1) the above issue number, 2) one sentence of what the item is about and why it's important.
Indicate whether you'd be willing to help out on the item.
Share the ETA if you're driving the item and have an guesstimate on when it will be done.
cc @apache/mxnet-committers
The text was updated successfully, but these errors were encountered: