mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Zha"<>
Subject Re: Release plan - MXNET 1.0.1
Date Thu, 18 Jan 2018 01:05:21 GMT
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
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
(might be hard to do, e.g. for optimizer). Otherwise, we must collectively decide that a feature
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,

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

View raw message