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

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

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

+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

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

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

[RESULT][LAZY VOTE] Next MXNet release

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 /

[LAZY VOTE] Next MXNet release

I calling a lazy vote to release MXNet 1.3.1 (patch release) and 1.4.0 (minor relase). Release content: release proposal page Target milestones: *1.3.1* - Code Freeze: 10/31 - Release published: