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

2019-07-13 Thread Sheng Zha 
Dear IPMC members,

It would be great if you could help with the vote. Thank you.

-sz

On 2019/07/10 09:33:34, Lai Wei  wrote: 
> Dear community,
> 
> This is a call for a releasing Apache MXNet (incubating) 1.5.0, release
> candidate 2.
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/50fe473a3e03c891caccb8cae8e5195bb740a4758f7688790dff70df@%3Cdev.mxnet.apache.org%3E
> 
> Result thread:
> https://lists.apache.org/thread.html/641cf0fddce623ff352ba9c7655938c0d16337bae4a8d290956ea130@%3Cdev.mxnet.apache.org%3E
> 
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.0.rc2/
> 
> The tag to be voted upon is 1.5.0.rc2:
> https://github.com/apache/incubator-mxnet/releases/tag/1.5.0.rc2
> 
> The release hash is 75a9e18:
> https://github.com/apache/incubator-mxnet/commit/75a9e187d00a8b7ebc71412a02ed0e3ae489d91f
> 
> Release artifacts are signed with the following key, 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/1.5.0+Release+Notes
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 release this package as ...
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> 
> Best Regards
> 
> Lai
> 

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

Re: New disclaimer text

2019-07-13 Thread Paul King 
+1

On Sat, Jul 13, 2019 at 10:44 AM Sheng Wu  wrote:

> +1 from me to have two disclaimers, chosen by podings.
>
> Also, +1 from me, the one they chosen should stay in website and
> announcement.
>
> Sheng
>
> Justin Mclean 于2019年7月13日 周六上午9:37写道：
>
> > Hi,
> >
> > +1 Works for me.
> >
> > It will need to be made very clear to podlings that different rules apply
> > depending on what disclaimer they have.
> >
> > Would this also please to the disclaimer on their web site and in
> > announcement emails?
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sheng Wu
> SkyWalking, Shardingsphere and Zipkin
>

Re: New disclaimer text

2019-07-13 Thread Sheng Wu 
Not good at naming stuff :) But I support to use different names.

Sheng Wu
Apache Skywalking, ShardingSphere, Zipkin



> 在 2019年7月14日，上午9:49，Craig Russell  写道：
> 
> It looks like we are closing on agreement to have (at least) two disclaimers. 
> Now we need to discuss naming. [1]
> 
> Two big choices here: 
> 
> DISCLAIMER.txt for both versions of disclaimer; or
> 
> DISCLAIMER.txt for the current standard disclaimer and some other name for 
> the new disclaimer.
> 
> If we choose another name:
> 
> DISCLAIMER2.txt
> DISCLAIMER-X.txt
> DISCLAIMER-L.txt
> 
> The advantage of keeping the same name for old and new disclaimers is there 
> is no need to change existing tools. But I'd argue that this violates the 
> principle of least surprise. If someone is reviewing a release, possibly with 
> the idea of redistributing it, they see DISCLAIMER.txt and think they know 
> what it contains, but it does not. Oops.
> 
> The advantage of changing the name with changed content is it highlights that 
> this is not the same disclaimer we all know and love. Which means the person 
> (or AI bot) reviewing the release is going to raise a flag to be looked at in 
> more detail. At that point, the reviewer (or human overseer) will notice that 
> the content is different and the release needs to have more scrutiny. Of 
> course, the disadvantage of this is that tooling will need to change to 
> accommodate the new disclosure. 
> 
> If we go down the path of changing the file name, I'd probably lean toward 
> DISCLAIMER-X.txt which sounds a bit scary until you read the disclaimer which 
> is much more scary than the file name.
> 
> Regards,
> 
> Craig
> 
> [1] The two hardest problems in computer science: cache invalidation, naming 
> and off-by-one
> https://martinfowler.com/bliki/TwoHardThings.html
> 
>> On Jul 12, 2019, at 7:04 PM, Dave Fisher  wrote:
>> 
>> +1 if as discussed earlier we enhance both disclaimers to include a link to 
>> the podling status page where the podling will provide the most up to date 
>> details.
>> 
>> We can discuss a new Git based status page in a separate thread. I’d like to 
>> change from the xml/secret yaml files in svn to a straight up markdown file 
>> in Git.
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Jul 12, 2019, at 5:44 PM, Sheng Wu  wrote:
>>> 
>>> +1 from me to have two disclaimers, chosen by podings.
>>> 
>>> Also, +1 from me, the one they chosen should stay in website and
>>> announcement.
>>> 
>>> Sheng
>>> 
>>> Justin Mclean 于2019年7月13日 周六上午9:37写道：
>>> 
 Hi,
 
 +1 Works for me.
 
 It will need to be made very clear to podlings that different rules apply
 depending on what disclaimer they have.
 
 Would this also please to the disclaimer on their web site and in
 announcement emails?
 
 Thanks,
 Justin
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 --
>>> Sheng Wu
>>> SkyWalking, Shardingsphere and Zipkin
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> Craig L Russell
> c...@apache.org
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: New disclaimer text

2019-07-13 Thread Craig Russell 
It looks like we are closing on agreement to have (at least) two disclaimers. 
Now we need to discuss naming. [1]

Two big choices here: 

DISCLAIMER.txt for both versions of disclaimer; or

DISCLAIMER.txt for the current standard disclaimer and some other name for the 
new disclaimer.

If we choose another name:

DISCLAIMER2.txt
DISCLAIMER-X.txt
DISCLAIMER-L.txt

The advantage of keeping the same name for old and new disclaimers is there is 
no need to change existing tools. But I'd argue that this violates the 
principle of least surprise. If someone is reviewing a release, possibly with 
the idea of redistributing it, they see DISCLAIMER.txt and think they know what 
it contains, but it does not. Oops.

The advantage of changing the name with changed content is it highlights that 
this is not the same disclaimer we all know and love. Which means the person 
(or AI bot) reviewing the release is going to raise a flag to be looked at in 
more detail. At that point, the reviewer (or human overseer) will notice that 
the content is different and the release needs to have more scrutiny. Of 
course, the disadvantage of this is that tooling will need to change to 
accommodate the new disclosure. 

If we go down the path of changing the file name, I'd probably lean toward 
DISCLAIMER-X.txt which sounds a bit scary until you read the disclaimer which 
is much more scary than the file name.

Regards,

Craig

[1] The two hardest problems in computer science: cache invalidation, naming 
and off-by-one
https://martinfowler.com/bliki/TwoHardThings.html

> On Jul 12, 2019, at 7:04 PM, Dave Fisher  wrote:
> 
> +1 if as discussed earlier we enhance both disclaimers to include a link to 
> the podling status page where the podling will provide the most up to date 
> details.
> 
> We can discuss a new Git based status page in a separate thread. I’d like to 
> change from the xml/secret yaml files in svn to a straight up markdown file 
> in Git.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On Jul 12, 2019, at 5:44 PM, Sheng Wu  wrote:
>> 
>> +1 from me to have two disclaimers, chosen by podings.
>> 
>> Also, +1 from me, the one they chosen should stay in website and
>> announcement.
>> 
>> Sheng
>> 
>> Justin Mclean 于2019年7月13日 周六上午9:37写道：
>> 
>>> Hi,
>>> 
>>> +1 Works for me.
>>> 
>>> It will need to be made very clear to podlings that different rules apply
>>> depending on what disclaimer they have.
>>> 
>>> Would this also please to the disclaimer on their web site and in
>>> announcement emails?
>>> 
>>> Thanks,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> --
>> Sheng Wu
>> SkyWalking, Shardingsphere and Zipkin
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Craig L Russell
c...@apache.org


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

[VOTE] Heron Release 0.20.1-incubating Release Candidate 3

2019-07-13 Thread Josh Fischer 
Hello Incubating Community,
This is a call for a vote to the 3rd release candidate for Apache Heron,
version v0.20.1-incubating. We request project mentors (binded) as well as
all contributors (unbinded) and users to review and vote on this incubator
release.



The tag to be voted upon:0.20.1-incubating-rc3
(40ccec635b45191593ff984a9ae81fd4e0a5dadd)The full list of changes and
release notes are available
at:
https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc3
<
https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc3
>Source
files can be found in dist.apache.org 
site:
https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-3/
<
https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-3/
>Source
SHA-512
checksums:68e2d4db598d73dc69e474dc82940402dc4689cc14dda14ad114cbaec79b1b3a8926625083e901f8234631f6345c6aa9e58fc0fec3176fce3e91e041e724d3b8
incubator-heron-0.20.1-incubating-rc3.tar.gz Please download the source
package, and follow the compiling
guide(
https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
<
https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
>)to
setup environment, build and run locally. Note that currently Bazel 0.26.0
is required to build this version.After Bazel is set up and works
correctly, you can use these release check scripts
(
https://github.com/apache/incubator-heron/blob/master/scripts/release_check/README.md#run-individual-release-checks
<
https://github.com/apache/incubator-heron/blob/master/scripts/release_check/README.md#run-individual-release-checks
>)
to verify the build.

The vote will be open for at least 72 hours or until the necessary number
of votes are reached.
Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
The Apache Heron (Incubating) Team

Re: [ANNOUNCE] Apache Training (incubating) - Navigating the ASF Incubator Process 1.0

2019-07-13 Thread Joshua Poore 
+1!

Joshua Poore


> On Jul 13, 2019, at 2:41 AM, Justin Mclean  wrote:
> 
> Hello Community,
> 
> The Apache Training (incubating) team is pleased to announce the source
> release of Navigating the ASF Incubator Process 1.0 (incubating).
> 
> This is a slide deck containing an overview of how to navigate the ASF
> incubating process from start to finish.
> 
> Apache Training aim is to create high-quality training material for various 
> projects in an open source form. Up until now everyone who wants to offer a 
> Training course for one of the Apache projects needs to create her or his 
> own slides/labs and keep them up-to-date. This is a significant investment 
> of time and money. This project aims to spread that burden and help all 
> Apache projects as we can create shared resources and we can also create 
> cross-project training resources.
> 
> The official source release are available from
> https://training.apache.org/downloads.html 
> .
> 
> If you have any usage questions, or have problems when upgrading, please
> don't hesitate to let us know by sending feedback to d...@training.apache.org 
> 
> or opening a GitHub issue at https://github.com/apache/?q=incubator-training 
> .
> 
> *Disclaimer*
> 
> Apache Training is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Incubator. Incubation is required of all
> newly accepted projects until a further review indicates that the
> infrastructure, communications, and decision making process have stabilized
> in a manner consistent with other successful ASF projects. While incubation
> status is not necessarily a reflection of the completeness or stability of
> the code, it does indicate that the project has yet to be fully endorsed by
> the ASF.
> 
> Thanks,
> Apache Training PPMC


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

Re: [ANNOUNCE] Apache Tuweni 0.8.0

2019-07-13 Thread Furkan KAMACI 
Congrats!

13 Tem 2019 Cmt, saat 11:58 tarihinde Pierre Smits 
şunu yazdı:

> Yay. First one out! Congrats to the team
>
> On Fri, 12 Jul 2019 at 00:51 Antoine Toulme  wrote:
>
> > Yes, I have sent a separate email to the users list, and an email to the
> > announce list.
> >
> > I however didn’t send it to the dev list.
> >
> > > On Jul 11, 2019, at 3:48 PM, larry mccay  wrote:
> > >
> > > Congrats, Antoine and Apache Tuweni (Incubating) Community!
> > > Have you sent a separate email to the dev@ and user@ tuweni lists as
> > well?
> > > If not, we should just include them on this one.
> > >
> > > On Thu, Jul 11, 2019 at 8:51 AM Jim Jagielski  wrote:
> > >
> > >> w00t!
> > >>
> > >>> On Jul 9, 2019, at 11:59 PM, Antoine Toulme 
> > wrote:
> > >>>
> > >>> The Apache Tuweni team is proud to announce the release of Apache
> > Tuweni
> > >>> (incubating) 0.8.0.
> > >>>
> > >>> Apache Tuweni is a set of libraries and other tools to aid
> development
> > of
> > >>> blockchain and other decentralized software in Java and other JVM
> > >>> languages. It includes a low-level bytes library, serialization and
> > >>> deserialization codecs (e.g. RLP), various cryptography functions
> > >>> and primatives, and lots of other helpful utilities. Tuweni is
> > >>> developed for JDK 1.8 or higher, and depends on various other FOSS
> > >> libraries.
> > >>>
> > >>> Apache Tuweni 0.8.0-incubating is our first release under the Apache
> > >> incubator.
> > >>> Source and binary distributions can be downloaded from:
> > >>> https://tuweni.apache.org/download
> > >>>
> > >>> Release notes are at:
> > >>> https://github.com/apache/incubator-tuweni/releases/tag/v0.8.0
> > >>>
> > >>> A big thank you to all the contributors in this milestone release!
> > >>>
> > >>> 
> > >>>
> > >>> Disclaimer: Apache Tuweni is an effort undergoing incubation at The
> > >> Apache
> > >>> Software Foundation (ASF), sponsored by the Apache Incubator.
> > Incubation
> > >> is
> > >>> required of all newly accepted projects until a further review
> > indicates
> > >>> that the infrastructure, communications, and decision making process
> > have
> > >>> stabilized in a manner consistent with other successful ASF projects.
> > >> While
> > >>> incubation status is not necessarily a reflection of the completeness
> > or
> > >>> stability of the code, it does indicate that the project has yet to
> be
> > >>> fully endorsed by the ASF.
> > >>>
> > >>> Please note the source distribution of Apache Tuweni contains a
> binary
> > >> file,
> > >>> the Gradle wrapper jar file. This file will be removed in the next
> > >> release.
> > >>> -
> > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>>
> > >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sent from my phone
>

Re: [ANNOUNCE] Apache Tuweni 0.8.0

2019-07-13 Thread Pierre Smits 
Yay. First one out! Congrats to the team

On Fri, 12 Jul 2019 at 00:51 Antoine Toulme  wrote:

> Yes, I have sent a separate email to the users list, and an email to the
> announce list.
>
> I however didn’t send it to the dev list.
>
> > On Jul 11, 2019, at 3:48 PM, larry mccay  wrote:
> >
> > Congrats, Antoine and Apache Tuweni (Incubating) Community!
> > Have you sent a separate email to the dev@ and user@ tuweni lists as
> well?
> > If not, we should just include them on this one.
> >
> > On Thu, Jul 11, 2019 at 8:51 AM Jim Jagielski  wrote:
> >
> >> w00t!
> >>
> >>> On Jul 9, 2019, at 11:59 PM, Antoine Toulme 
> wrote:
> >>>
> >>> The Apache Tuweni team is proud to announce the release of Apache
> Tuweni
> >>> (incubating) 0.8.0.
> >>>
> >>> Apache Tuweni is a set of libraries and other tools to aid development
> of
> >>> blockchain and other decentralized software in Java and other JVM
> >>> languages. It includes a low-level bytes library, serialization and
> >>> deserialization codecs (e.g. RLP), various cryptography functions
> >>> and primatives, and lots of other helpful utilities. Tuweni is
> >>> developed for JDK 1.8 or higher, and depends on various other FOSS
> >> libraries.
> >>>
> >>> Apache Tuweni 0.8.0-incubating is our first release under the Apache
> >> incubator.
> >>> Source and binary distributions can be downloaded from:
> >>> https://tuweni.apache.org/download
> >>>
> >>> Release notes are at:
> >>> https://github.com/apache/incubator-tuweni/releases/tag/v0.8.0
> >>>
> >>> A big thank you to all the contributors in this milestone release!
> >>>
> >>> 
> >>>
> >>> Disclaimer: Apache Tuweni is an effort undergoing incubation at The
> >> Apache
> >>> Software Foundation (ASF), sponsored by the Apache Incubator.
> Incubation
> >> is
> >>> required of all newly accepted projects until a further review
> indicates
> >>> that the infrastructure, communications, and decision making process
> have
> >>> stabilized in a manner consistent with other successful ASF projects.
> >> While
> >>> incubation status is not necessarily a reflection of the completeness
> or
> >>> stability of the code, it does indicate that the project has yet to be
> >>> fully endorsed by the ASF.
> >>>
> >>> Please note the source distribution of Apache Tuweni contains a binary
> >> file,
> >>> the Gradle wrapper jar file. This file will be removed in the next
> >> release.
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Sent from my phone