+1 sounds like an acceptible work-around to me.
Thanks Joe!
Sam
On 6/3/22, 11:20 AM, "Joe Evans" wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know the
content is safe.
In order
Thanks Joe & community for continuing to push this along.
Given that this release process has drawn on quite a while, would it be
possible to pull in PR #20137 [1]? This goes along with #20107 [2] that was
part of 1.9.0.rc7 [3] for deconvolution support. I would be happy to do the
backporting.
+1 tested extensions examples on CPU
Sam
On 6/7/21, 8:51 AM, "detected-as-s...@amazon.com on behalf of Przemysław
Trędak" wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know the
content
Hi kezhenxu94,
The keys file is at:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS (in the "dev"
directory) until after the release vote concludes. Once the release vote is
complete and passes, we publish to the "release" directory in
https://dist.apache.org/repos/dist/release/inc
Dear all,
The Apache MXNet (incubating) community is happy to announce Apache MXNet
(incubating) version 1.8.0!
Apache MXNet (incubating) is a deep learning framework designed for both
efficiency and flexibility. It allows you to mix symbolic and imperative
programming to maximize efficiency a
2021/01/22 20:03:27, "Skalicky, Sam" wrote:
> Dear MXNet Community,
>
> Im happy to announce the results of the vote.
> This vote passes with 8 +1 votes (3 binding) and no 0 or -1 votes
>
> +1 votes
> * Sheng Zha (binding)
> * Joe Evans
+1
Id prefer to refer to old issues and start new ones. Often the similar error
message is not relevant as codebase has changed and the original steps to
reproduce are no longer valid. Like Sheng said this warrants a whole new set of
info so it might as well go into a new issue entirely to avoi
Thanks Justin,
We were confused looking at the release guidelines on the incubator [1] doesn’t
seem to call out that the required "three +1 votes are required and more +1
votes than -1 votes" should come from PPMC members. All it says is that the
vote be held on the public dev list. Following t
+1
Built linux CPU config on c5.18xl and ran all extension examples
Built linux GPU config on g4dn.16xl and ran the GPU custom op example (relu) &
subgraph example from extensions
Sam
On 2/3/21, 7:23 AM, "Leonard Lausen" wrote:
CAUTION: This email originated from outside of the organizat
Thanks Leonard for starting this exciting release for the 2.0.0 alpha!
I built and tested the linux CPU build on c5.18xl and ran all of the extensions
examples. The subgraph example is failing [1], but all other examples pass.
-1 due to [1]
Sam
[1] https://github.com/apache/incubator-mxnet/is
; > *Tough things take a bit longer to complete. But often the rewards are
very
> > sweet!*
> >
> > Let's get this release to the finish line!
> > Cheers,
> > Chai
> >
> >
> > On Wed, 20 Jan 20
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.8.0. Voting
will start January 19, 17:00:00 PT and close on January 21, 17:00:00 PT.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.8.0+Release+Notes
Link to release candidate:
htt
se -Bbuild \
> -DUSE_MKLDNN=OFF -DMXNET_CUDA_ARCH="6.0 6.1 7.0 7.5 8.0" \
> -DUSE_CUDA=ON -DUSE_CUDNN=1 \
> -DUSE_NCCL=ON \
> -DUSE_DIST_KVSTORE=ON \
> -DONNX_NAMESPACE=onnx \
> -DUSE_NVTX=1 \
> -DUSE_INTGEMM=OF
+3 (one vote for me, myself, and I :-D)
On 11/3/20, 4:13 PM, "Marco de Abreu" wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know the
content is safe.
I think it's a good idea to m
python/gpu/ folder.
> >>
> >> [1]
> >>
>
https://github.com/apache/incubator-mxnet/blob/1.8.0.rc2/docs/static_site/src/pages/get_started/build_from_source.md#building-mxnet
> >> [2]
> >>
>
https://github.com/apache/incubator
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.8.0. Voting
will start October 29, 20:10:00 PT and close on November 1, 20:10:00 PT.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.8.0+Release+Notes
Link to release candidate:
http
mxnet/issues/19427
On 10/21/20, 3:32 PM, "Skalicky, Sam" wrote:
Hi MXNet Community,
The vote on Apache general has identified some issues [1] that need to be
resolved before we can release 1.8.0.
There are currently 3 main issues that need to be resolved:
1. Updating
/apache/incubator-mxnet/pull/19402
On 10/12/20, 10:21 PM, "Skalicky, Sam" wrote:
Dear MXNet Community,
Im happy to announce the results of the vote.
This vote passes with 5 +1 votes (3 binding) and no 0 or -1 votes
+1 votes
* Sheng Zha (binding)
* Sandeep Kr
Thanks for starting this discussion Zhaoqi!
Previously we had decided to support 2 major versions of CUDA, since we
recently dropped support for CUDA 9 now we only support CUDA 10 & 11. Im not
opposed to changing the standard, but we should think about the impact for
users. Upgrading is painful
safe.
+1
On 2020/10/09 22:50:13, Yang Shi wrote:
> +1
>
> On 2020/10/06 21:25:38, "Skalicky, Sam"
wrote:
> > Dear MXNet community,
> >
> > This is the vote to release Apache MXNet (incubating) version 1.8.0.
Voting will start
Correction on close of voting month: September --> October
On 10/6/20, 2:26 PM, "Skalicky, Sam" wrote:
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.8.0. Voting
will start October 6, 23:59:59 PDT and close on October 9, 23:59:59 P
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.8.0. Voting
will start October 6, 23:59:59 PDT and close on September 9, 23:59:59 PDT.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.8.0+Release+Notes
Link to release candidate:
ht
github.com/apache/incubator-mxnet/pull/19251
[4] https://github.com/apache/incubator-mxnet/pull/19267
[5] https://github.com/apache/incubator-mxnet/pull/19278
On 9/30/20, 9:53 PM, "Skalicky, Sam" wrote:
Thanks Leonard for picking up this work. Are you planning to open another
P
to squash commits during
porting from one branch to another which reduces false positives in git
cherry
mode (commits detected as missing that were actually ported).
Best regards
Leonard
On Wed, 2020-09-30 at 21:52 +, Skalicky, Sam wrote:
> Hi MXNet Community,
the discussion and get the remaining votes necessary.
Thanks!
Sam
On 9/29/20, 12:41 PM, "Skalicky, Sam" wrote:
There was no response from the community on the discussion thread [1]. So
the current state is the same.
[1]
https://lists.apache.org/t
ovements would be great [2].
Thanks
Leonard
[1]: https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.8.0.rc0/
[2]: https://github.com/apache/incubator-mxnet/issues/18666
>
>
> On Mon, Sep 28, 2020 at 11:36 AM Skalicky, Sam
&g
. This is exciting given
> it is coming with CUDA11 and cuDNN8!!
>
> Fixing the release candidate link:
> https://github.com/apache/incubator-mxnet/releases/tag/1.8.0.rc0
>
> Best,
> Sandeep
>
>
> On Fri, Sep 25, 2020 at 11:24 PM
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.8.0. Voting
will start September 26, 23:59:59 PDT and close on September 29, 23:59:59 PDT.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.8.0+Release+Notes
Link to release candidate
Thanks Sam! Do we have an automated method to ensure all prs are present in
the appropriate branches? Maybe compare the underlying commits of prs or
the content.
-Marco
On Sun, Sep 20, 2020, 07:22 Skalicky, Sam
wrote:
> Hi MXNet Community,
>
> As we
] https://github.com/apache/incubator-mxnet/pull/19196
[4] https://github.com/apache/incubator-mxnet/pull/18649
[5] https://github.com/apache/incubator-mxnet/pull/18220
[6] https://github.com/apache/incubator-mxnet/pull/18261
[7] https://github.com/apache/incubator-mxnet/pull/18482
From: "Ska
Hi MXNet Community,
Thanks to Ciyong and the Intel folks the 1.7.0 release of MXNet has completed!
We’ve been tracking the subsequent 1.8.0 release here [1] for a couple months
now. Our next milestone is feature/code freeze on September 18th. If you are
planning to include any other features in
+1 for pulling the discussion/questions into closer proximity to the devs so we
can more easily address one of the recent concerns that people asking questions
on discuss aren’t getting responses from devs.
Sam
On 8/28/20, 11:41 AM, "Sheng Zha" wrote:
CAUTION: This email originated from
32 matches
Mail list logo
