Re: [RESTARTING][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Justin Mclean]

HI,

> based on Justin's and community feedback I'm suggesting to restart the vote.

That wasn’t my suggestion. I was just pointing out you closed the vote too 
early.

I'd suggest you fix the issue and call another vote on you dev list and then 
bring it back to the incubator to vote, you could probably do this fairly 
quickly (if the PPMC agrees) not observing the usual 74 hour waiting period as 
the changes are minimal and are likely to not include code changes.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESTARTING][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Lin Yuan]

+1 binding
Horovod is going to release it's 0.16.0 in the coming week with MXNet
integration. We need to release 1.4.0 which includes all the dependencies
for Horovod integration.

Best,

Lin

On Mon, Feb 11, 2019 at 9:30 PM Steffen Rochel 
wrote:

> Dear community -
> based on Justin's and community feedback I'm suggesting to restart the
> vote.
> Current status:
> binding votes:
> +1: 2 votes (Henri, Jason)
> -1:  1 vote (Luciano)
>
> non-binding:
> +1: 1 vote (Kellen)
>
> The community is investigating feedback from Luciano that the exclusion
> file is to broad and potentially missing files which can and must have
> apache license headers not to be checked.
>
> Regards,
> Steffen
>
>
>
>
> On Mon, Feb 11, 2019 at 10:08 AM Hagay Lupesko  wrote:
>
> > Based on Justin's feedback, can we resume the vote instead of cancelling
> > it?
> >
> > On Mon, Feb 11, 2019 at 12:02 AM Justin Mclean  >
> > wrote:
> >
> > > Hi,
> > >
> > > In future don’t be so hasty to cancel a release vote, people mind can
> be
> > > changed and a -1 is not a veto on a release.
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

[RESTARTING][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Steffen Rochel]

Dear community -
based on Justin's and community feedback I'm suggesting to restart the vote.
Current status:
binding votes:
+1: 2 votes (Henri, Jason)
-1:  1 vote (Luciano)

non-binding:
+1: 1 vote (Kellen)

The community is investigating feedback from Luciano that the exclusion
file is to broad and potentially missing files which can and must have
apache license headers not to be checked.

Regards,
Steffen




On Mon, Feb 11, 2019 at 10:08 AM Hagay Lupesko  wrote:

> Based on Justin's feedback, can we resume the vote instead of cancelling
> it?
>
> On Mon, Feb 11, 2019 at 12:02 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > In future don’t be so hasty to cancel a release vote, people mind can be
> > changed and a -1 is not a veto on a release.
> >
> > Thanks,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Luciano Resende]

On Mon, Feb 11, 2019 at 3:55 PM Hen  wrote:
>
> Did you mean:
>
> "The rat-exclude configuration on the project _must_ be less permissive."
>
> ?
>

What I was trying to say is that, even though MXNet has configured and
is using rat, the rat-exclude then is very broad, where it excludes
like (*.xml which leave pom.xml out for example, or docker/*) this
causes a lot of files that can ahd must have apache license headers to
not be checked.

> (your text suggests it's an option, whereas your vote says it's required)
>

https://www.apache.org/legal/src-headers.html

> On Sun, Feb 10, 2019 at 8:08 PM Luciano Resende 
> wrote:
>
> > I ran RAT, and while I understand that a lot of the failures are
> > coming from the 3rdparty directory, some of those are from files that
> > should have the ASF license header such as pom files, docker files,
> > project documentation (yes, MD files do accept apache license
> > headers),  Maybe the rat-exclude configuration on the project should
> > be less permissive.
> >
> > Based on this I am -1 (binding)
> >
> > On Wed, Feb 6, 2019 at 1:59 PM Steffen Rochel 
> > wrote:
> > >
> > > Dear community,
> > >
> > > This is a call for releasing Apache MXNet (incubating) 1.4.0, release
> > > candidate 2
> > >
> > > Apache MXNet (incubating) community has voted and approved the release.
> > >
> > > Vote thread:
> > >
> > >
> > https://lists.apache.org/thread.html/4b445460d36d098be1c1e60e29869cf243e2bc37bd2b84ca7b1daab3@%3Cdev.mxnet.apache.org%3E
> > >
> > >
> > > Result thread:
> > >
> > >
> > https://lists.apache.org/thread.html/60e3272326cf93100370fa5b01a54a4b2f18f95462553b5a1acfd456@%3Cdev.mxnet.apache.org%3E
> > >
> > > The community raised the following issues which are not considered as
> > > release stopper:
> > >
> > > 1. NOTICE year is wrong (2018): Not considered a stopping issue as
> > release
> > > was started in 2018.
> > > 2. TVM NOTICE missing - TVM NOTICE file was added post the commit ID used
> > > in MXNet v1.4.0.rc2 release, not considered a stopping issue
> > > 3. build with make passes, but build with cmake failed in
> > > 3rdparty/dmlc-core/test/unittest
> > > 4. Recent MKLDNN upgrade prevents us from offering binary distribution
> > for
> > > earlier versions before OSX 10.13.
> > >
> > >
> > > The source tarball, including signatures, digests, etc. can be found at:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc2/
> > >
> > > The tag to be voted upon:
> > > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc2
> > >
> > > The release hash is e999a46
> > > <
> > https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26
> > >
> > > :
> > >
> > >
> > https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26
> > >
> > > KEYS file available:
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> > >
> > > For information about the contents of this release, see:
> > >
> > https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
> > >
> > > The vote will be open at least 72 hours (Sunday February 10th 4pm PST)
> > and
> > > until sufficient votes are received.
> > >
> > > [ ] +1 release this package as 1.4.0
> > > [ ] +0 no opinion
> > > [ ] -1 do not release this package because...
> > >
> > > Best regards,
> > > Steffen
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Hen]

Did you mean:

"The rat-exclude configuration on the project _must_ be less permissive."

?

(your text suggests it's an option, whereas your vote says it's required)

On Sun, Feb 10, 2019 at 8:08 PM Luciano Resende 
wrote:

> I ran RAT, and while I understand that a lot of the failures are
> coming from the 3rdparty directory, some of those are from files that
> should have the ASF license header such as pom files, docker files,
> project documentation (yes, MD files do accept apache license
> headers),  Maybe the rat-exclude configuration on the project should
> be less permissive.
>
> Based on this I am -1 (binding)
>
> On Wed, Feb 6, 2019 at 1:59 PM Steffen Rochel 
> wrote:
> >
> > Dear community,
> >
> > This is a call for releasing Apache MXNet (incubating) 1.4.0, release
> > candidate 2
> >
> > Apache MXNet (incubating) community has voted and approved the release.
> >
> > Vote thread:
> >
> >
> https://lists.apache.org/thread.html/4b445460d36d098be1c1e60e29869cf243e2bc37bd2b84ca7b1daab3@%3Cdev.mxnet.apache.org%3E
> >
> >
> > Result thread:
> >
> >
> https://lists.apache.org/thread.html/60e3272326cf93100370fa5b01a54a4b2f18f95462553b5a1acfd456@%3Cdev.mxnet.apache.org%3E
> >
> > The community raised the following issues which are not considered as
> > release stopper:
> >
> > 1. NOTICE year is wrong (2018): Not considered a stopping issue as
> release
> > was started in 2018.
> > 2. TVM NOTICE missing - TVM NOTICE file was added post the commit ID used
> > in MXNet v1.4.0.rc2 release, not considered a stopping issue
> > 3. build with make passes, but build with cmake failed in
> > 3rdparty/dmlc-core/test/unittest
> > 4. Recent MKLDNN upgrade prevents us from offering binary distribution
> for
> > earlier versions before OSX 10.13.
> >
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc2/
> >
> > The tag to be voted upon:
> > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc2
> >
> > The release hash is e999a46
> > <
> https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26
> >
> > :
> >
> >
> https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> >
> > For information about the contents of this release, see:
> >
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
> >
> > The vote will be open at least 72 hours (Sunday February 10th 4pm PST)
> and
> > until sufficient votes are received.
> >
> > [ ] +1 release this package as 1.4.0
> > [ ] +0 no opinion
> > [ ] -1 do not release this package because...
> >
> > Best regards,
> > Steffen
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [CANCELLED][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Hagay Lupesko]

Based on Justin's feedback, can we resume the vote instead of cancelling it?

On Mon, Feb 11, 2019 at 12:02 AM Justin Mclean 
wrote:

> Hi,
>
> In future don’t be so hasty to cancel a release vote, people mind can be
> changed and a -1 is not a veto on a release.
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Suitable project name search (was: [PROPOSAL] New blockchain project: Cava)

[Antoine Toulme]

Thanks Pierre. Sorry, I was trying to spare myself looking ignorant, and I 
ended up breaking public comms.

Thanks for the advice, I’ll proceed.

> On Feb 11, 2019, at 12:28 AM, Pierre Smits  wrote:
> 
> Hi Antoine,
> 
> I suggest to include the general@incubator.a.o mailing list as it will allow 
> other Apache contributors to chime in (maybe even faster than I am).
> 
> Regarding the search for the optimal name, the best way to go about (IMO) is 
> to make a short list - in accordance with [1] - and discuss those on list 
> with the community. When a satisfactory result has been achieved use that in 
> the proposal and [2]
> 
> 
> [1] https://incubator.apache.org/guides/names.html 
> [2] 
> https://issues.apache.org/jira/projects/PODLINGNAMESEARCH 
> 
> 
> Best regards,
> 
> Pierre Smits
> 
> Apache Trafodion , Vice President
> Apache Directory , PMC Member
> Apache Incubator , committer
> Apache OFBiz , contributor (without privileges) 
> since 2008
> Apache Steve , committer
> 
> 
> On Fri, Feb 8, 2019 at 6:34 PM Antoine Toulme  > wrote:
> Hi Pierre,
> 
> Looking over Jira, all the tickets are about proving a name that has already 
> been selected is not currently in use.
> 
> I was looking for a way to conduct a name search with the community, with 
> proposals.
> Is jira the right avenue for this?
> 
> If not, I’m happy to swing it by selecting a name of my own choosing.
> 
> Cheers,
> 
> Antoine
> 
>> On Feb 8, 2019, at 12:46 AM, Pierre Smits > > wrote:
>> 
>> 
>> Hi Antoine,
>> 
>> First of all: thank you for the LinkedIn accept.
>> 
>> More information about the PNS (Podling Name Search) can be found via [1]. 
>> 
>> After having yourself familiarised with that, I suggest to register a JIRA 
>> ticket with project 'PODLING NAME SEARCH' for the new project name, see [2]. 
>> I
>>  also suggest to browse through a few of the open tickets to get a gist of 
>> what steps to take.
>> 
>> [1] https://incubator.apache.org/guides/names.html 
>> 
>> [2] https://issues.apache.org/jira/projects/PODLINGNAMESEARCH 
>> 
>> 
>> Best regards,
>> 
>> Pierre Smits
>> 
>> Apache Trafodion , Vice President
>> Apache Directory , PMC Member
>> Apache Incubator , committer
>> Apache OFBiz , contributor (without privileges) 
>> since 2008
>> Apache Steve , committer
>> 
>> 
>> On Fri, Feb 8, 2019 at 3:03 AM Antoine Toulme > > wrote:
>> [going off-list]
>> 
>> How should we conduct the name search?
>> 
>> I have a few names I can submit. I can push for one if that makes sense.
>> 
>> I am looking for previous discussions on the list, but nothing close to an 
>> open name search seems to have happened there.
>> 
>> Please help?
>> 
>> Cheers,
>> 
>> Antoine
> 

Re: Suitable project name search (was: [PROPOSAL] New blockchain project: Cava)

[Christofer Dutz]

And building awareness, reputation and community around something is quite a 
lot of work. 
So If you start a new podling and work hard on promoting it, it would be a 
shame having to rename that and effectively loose all promotional results you 
might have had.
I would also strongly suggest to do the Name-Search first, even if you're not 
required to.

Chris


Am 11.02.19, 09:48 schrieb "Justin Mclean" :

Hi,

A name search is not needed before going the incubator, however changing a 
project name does have a cost both infra wise and community wise, so it be to 
come up with a name that likely be unique in project the project does.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Suitable project name search (was: [PROPOSAL] New blockchain project: Cava)

[Justin Mclean]

Hi,

A name search is not needed before going the incubator, however changing a 
project name does have a cost both infra wise and community wise, so it be to 
come up with a name that likely be unique in project the project does.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Suitable project name search (was: [PROPOSAL] New blockchain project: Cava)

[Pierre Smits]

Hi Antoine,

I suggest to include the general@incubator.a.o mailing list as it will
allow other Apache contributors to chime in (maybe even faster than I am).

Regarding the search for the optimal name, the best way to go about (IMO)
is to make a short list - in accordance with [1] - and discuss those* on
list* with the community. When a satisfactory result has been achieved use
that in the proposal and [2]


[1] https://incubator.apache.org/guides/names.html
[2] https://issues.apache.org/jira/projects/PODLINGNAMESEARCH

Best regards,

Pierre Smits

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer


On Fri, Feb 8, 2019 at 6:34 PM Antoine Toulme  wrote:

> Hi Pierre,
>
> Looking over Jira, all the tickets are about proving a name that has
> already been selected is not currently in use.
>
> I was looking for a way to conduct a name search with the community, with
> proposals.
> Is jira the right avenue for this?
>
> If not, I’m happy to swing it by selecting a name of my own choosing.
>
> Cheers,
>
> Antoine
>
> On Feb 8, 2019, at 12:46 AM, Pierre Smits  wrote:
>
>
> Hi Antoine,
>
> First of all: thank you for the LinkedIn accept.
>
> More information about the PNS (Podling Name Search) can be found via [1].
>
> After having yourself familiarised with that, I suggest to register a JIRA
> ticket with project 'PODLING NAME SEARCH' for the new project name, see
> [2]. I
>  also suggest to browse through a few of the open tickets to get a gist of
> what steps to take.
>
> [1] https://incubator.apache.org/guides/names.html
> [2] https://issues.apache.org/jira/projects/PODLINGNAMESEARCH
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without
> privileges) since 2008*
> Apache Steve , committer
>
>
> On Fri, Feb 8, 2019 at 3:03 AM Antoine Toulme  wrote:
>
>> [going off-list]
>>
>> How should we conduct the name search?
>>
>> I have a few names I can submit. I can push for one if that makes sense.
>>
>> I am looking for previous discussions on the list, but nothing close to
>> an open name search seems to have happened there.
>>
>> Please help?
>>
>> Cheers,
>>
>> Antoine
>
>
>

Re: [CANCELLED][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Justin Mclean]

Hi,

In future don’t be so hasty to cancel a release vote, people mind can be 
changed and a -1 is not a veto on a release.

Thanks,
Justin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org