mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steffen Rochel <>
Subject Re: Release plan - MXNET 1.0.1
Date Tue, 23 Jan 2018 15:51:36 GMT
Hi Sheng -
1. branch usage and versioning - lets converge our discussion and document
the agreement on wiki. I started a draft summarizing my understanding of
the proposal at
Lets work together to refine and clarify the draft, so we have clarity
going forward. I'm inviting everyone to contribute to this discussion.
As MKLDNN integration is not ready yet and we want to release all the good
improvements including updates in tutorials and documentation I suggest we
move forward with the release asap. As we don't have major features or
non-compatible API changes (to best of my knowledge) I think it is
appropriate to label the release as 1.0.1.
Note: This label indicates a patch release. Patch releases should be
created from the related release branch. As we didn't plan for it and to
minimize overhead I suggest we make a one time exception to cut the 1.0.1
release from master branch and clearly communicate in release notes. Going
forward we should follow the methodology for versioning and branching to
whatever we agree on.
2. Disabled tests: I agree with your concerns that we had to disable 13
tests due to non-deterministic behavior (see issues
<>). I'm calling on
all contributors to help to resolve the non-deterministic behavior, so we
can improve our test coverage. As we discussed offline, lets tests manually
short term, document the known issue in the release notes and prioritize
efforts post 1.0.1 release.


On Wed, Jan 17, 2018 at 5:05 PM Sheng Zha <> wrote:

> Hi Haibin,
> Thanks for leading this. I suggest that we hold onto this release until we
> have clarity on the following items.
> 1. branch usage and versioning
> Given that we are past 1.0 and we're changing APIs, I'd like to suggest
> that we first agree on how
> versioning works in mxnet. If we follow semantic versioning, it would
> suggest that features like
> MKL-DNN should go at least into 1.1 (minor version change) instead of
> 1.0.1 (patch release).
> Also, assuming that new release will come from a new forked branch, I
> suggest that we clarify on how to
> name the branches too.
> You can find relevant thread at
> 2. disabled tests
> For the purpose of stabilizing test automation system, many tests were
> disabled. In order to avoid
> releasing untested features, we should mitigate the situation of having
> disabled tests.
> That means we can fix the tests before the release, or remove the
> corresponding feature from release
> (might be hard to do, e.g. for optimizer). Otherwise, we must collectively
> decide that a feature is
> OK to release without tests.
> The thread on this topic can be found at
> We can proceed on the release with more confidence once we have clarity.
> Best regards,
> -sz
> On 2018-01-10 15:33, Haibin Lin <> wrote:
> > I am starting the process to prepare for MXNET 1.0.1 release. I have
> > drafted release notes
> > (*
> > <
> >*)
> > to cover the tasks under this release.
> >
> > A release candidate will be cut on Monday 22nd Jan, 2018 and voting will
> > commence from then till Thursday 25th Jan, 2018. If you have any
> additional
> > features in progress and would like to include it in this release, please
> > assure they have been merged by Thursday 18th Jan, 2018 with comment so I
> > may update the release notes.
> >
> > Feel free to add any other comments/suggestions.
> >
> > Thanks,
> > Haibin
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message