Re: MXNet 1.2 release question ?
Hi Hen, The project didn't publish any such guaranteed timeline for releases. What I meant with "late with release" was that this release had taken more time than any previous releases that I can recall. Anirudh On Tue, May 15, 2018 at 9:43 PM, Hen wrote: > I don’t understand what “late with the release” means. Did the project > publish a timeline of releases that it guaranteed or something? > > On Mon, May 14, 2018 at 10:11 AM Anirudh wrote: > > > Hi all, > > > > Our vote got blocked on general@ list. The main reason was the inclusion > > of > > a file with category b license in non binary form: > > "3rdparty/googletest/googlemock/docs/DevGuide.md". > > This file needs to be removed from source. > > > > There are two options we have right now: > > > > 1. Remove the DevGuide.md from source and call for a new vote. > > 2. Remove the DevGuide.md, fix some other license issues and also fix > some > > other issues: compilation issues on older versions of mac 10.10 or older, > > push other fixes etc. > > > > The first option would happen much quicker, since there is no change in > > source apart from removal of DevGuide.md file and we can close the vote > > quicker when the quorum is reached. > > > > The second option will have to go through the full vote cycle again but > > will fix some issues with previous RC. > > > > I am inclined to do 1 currently since I don't see the compilation issue > on > > older version of Mac as a critical one and we are already considerably > late > > with the release. > > > > I would like to know what you guys think. > > > > Anirudh > > >
Re: MXNet 1.2 release question ?
I don’t understand what “late with the release” means. Did the project publish a timeline of releases that it guaranteed or something? On Mon, May 14, 2018 at 10:11 AM Anirudh wrote: > Hi all, > > Our vote got blocked on general@ list. The main reason was the inclusion > of > a file with category b license in non binary form: > "3rdparty/googletest/googlemock/docs/DevGuide.md". > This file needs to be removed from source. > > There are two options we have right now: > > 1. Remove the DevGuide.md from source and call for a new vote. > 2. Remove the DevGuide.md, fix some other license issues and also fix some > other issues: compilation issues on older versions of mac 10.10 or older, > push other fixes etc. > > The first option would happen much quicker, since there is no change in > source apart from removal of DevGuide.md file and we can close the vote > quicker when the quorum is reached. > > The second option will have to go through the full vote cycle again but > will fix some issues with previous RC. > > I am inclined to do 1 currently since I don't see the compilation issue on > older version of Mac as a critical one and we are already considerably late > with the release. > > I would like to know what you guys think. > > Anirudh >
Re: MXNet 1.2 release question ?
Justin's -1 does not block the release if we can get one more +1. Do we have one more mentor or someone else who can +1 the release in general list? On Mon, May 14, 2018 at 1:01 PM, Anirudh wrote: > Hi all, > > I am going to proceed with option 1. Please let me know now, if you have > any concerns. > > Anirudh > > On Mon, May 14, 2018 at 10:11 AM, Anirudh wrote: > > > Hi all, > > > > Our vote got blocked on general@ list. The main reason was the inclusion > > of a file with category b license in non binary form: > "3rdparty/googletest/ > > googlemock/docs/DevGuide.md". > > This file needs to be removed from source. > > > > There are two options we have right now: > > > > 1. Remove the DevGuide.md from source and call for a new vote. > > 2. Remove the DevGuide.md, fix some other license issues and also fix > some > > other issues: compilation issues on older versions of mac 10.10 or older, > > push other fixes etc. > > > > The first option would happen much quicker, since there is no change in > > source apart from removal of DevGuide.md file and we can close the vote > > quicker when the quorum is reached. > > > > The second option will have to go through the full vote cycle again but > > will fix some issues with previous RC. > > > > I am inclined to do 1 currently since I don't see the compilation issue > on > > older version of Mac as a critical one and we are already considerably > late > > with the release. > > > > I would like to know what you guys think. > > > > Anirudh > > >
Re: MXNet 1.2 release question ?
Hi all, I am going to proceed with option 1. Please let me know now, if you have any concerns. Anirudh On Mon, May 14, 2018 at 10:11 AM, Anirudh wrote: > Hi all, > > Our vote got blocked on general@ list. The main reason was the inclusion > of a file with category b license in non binary form: "3rdparty/googletest/ > googlemock/docs/DevGuide.md". > This file needs to be removed from source. > > There are two options we have right now: > > 1. Remove the DevGuide.md from source and call for a new vote. > 2. Remove the DevGuide.md, fix some other license issues and also fix some > other issues: compilation issues on older versions of mac 10.10 or older, > push other fixes etc. > > The first option would happen much quicker, since there is no change in > source apart from removal of DevGuide.md file and we can close the vote > quicker when the quorum is reached. > > The second option will have to go through the full vote cycle again but > will fix some issues with previous RC. > > I am inclined to do 1 currently since I don't see the compilation issue on > older version of Mac as a critical one and we are already considerably late > with the release. > > I would like to know what you guys think. > > Anirudh >
MXNet 1.2 release question ?
Hi all, Our vote got blocked on general@ list. The main reason was the inclusion of a file with category b license in non binary form: "3rdparty/googletest/googlemock/docs/DevGuide.md". This file needs to be removed from source. There are two options we have right now: 1. Remove the DevGuide.md from source and call for a new vote. 2. Remove the DevGuide.md, fix some other license issues and also fix some other issues: compilation issues on older versions of mac 10.10 or older, push other fixes etc. The first option would happen much quicker, since there is no change in source apart from removal of DevGuide.md file and we can close the vote quicker when the quorum is reached. The second option will have to go through the full vote cycle again but will fix some issues with previous RC. I am inclined to do 1 currently since I don't see the compilation issue on older version of Mac as a critical one and we are already considerably late with the release. I would like to know what you guys think. Anirudh
