[RESULT] [VOTE] Release Apache APISIX (incubating) 1.4

2020-06-29 Thread Nirojan Selvanathan 
Hi all,

Release vote for Release Apache APISIX (Incubating) 1.4 has PASSED and
closed now.

The results are as follows:
4 IPMC +1 votes:
- Justin Mclean
- Kevin
- Willem Jiang
- Sheng Wu

9 + 1 votes:
- YuanSheng Wang
- Junxu Chen
- Zhiyuan Ju
- Wei Liu
- Sunyi
- Jinwei
- Linsir Wu
- Ming Wen
- Li Ling

Vote thread:
https://lists.apache.org/thread.html/r3304413b3d69f8d388c9f42714616776d6148f7eb674794861edc790%40%3Cdev.apisix.apache.org%3E

I will now proceed to publish the source release of Apache APISIX
(incubating) 1.4

Thank you.

-- 
Best Regards,
S.Nirojan
Linked-in

Announcing ApacheCon @Home 2020

2020-06-29 Thread Rich Bowen 

Hi, Apache enthusiast!

(You’re receiving this because you’re subscribed to one or more dev or 
user mailing lists for an Apache Software Foundation project.)


The ApacheCon Planners and the Apache Software Foundation are pleased to 
announce that ApacheCon @Home will be held online, September 29th 
through October 1st, 2020. We’ll be featuring content from dozens of our 
projects, as well as content about community, how Apache works, business 
models around Apache software, the legal aspects of open source, and 
many other topics.


Full details about the event, and registration, is available at 
https://apachecon.com/acah2020


Due to the confusion around how and where this event was going to be 
held, and in order to open up to presenters from around the world who 
may previously have been unable or unwilling to travel, we’ve reopened 
the Call For Presentations until July 13th. Submit your talks today at 
https://acna2020.jamhosted.net/


We hope to see you at the event!
Rich Bowen, VP Conferences, The Apache Software Foundation

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

Announcing ApacheCon @Home 2020

2020-06-29 Thread Rich Bowen 

Dear PMCs and Incubating projects,

Since I know that some incubating projects won't have seen my 
announcements to dev@ and user@ lists, I am repeating it here. I 
apologize for anyone who has already seen this one or more times.


We’re pleased to announce that ApacheCon 2020 will be held online, 
September 29th through October 1st, 2020. You can see the full details 
in the various other announcements that have been going out to other 
lists you’re on, so I won’t repeat all of that again here.


My message for you is that, due to the online nature of the event, we’re 
freed of the normal space/time constraints that we have to deal with at 
in-person events. We can have pretty much as much content as we want, on 
as many topics as we want.


If your project (or family of projects) wants to have a presence at 
ApacheCon, from one “what is it?” talk all the way up to a full track of 
content, please get in touch with me - rbo...@apache.org - as soon as 
possible to arrange that.


We are on a very short timeline, due to a long list of blockers that we 
have had to deal with over the past few months, and so please don’t 
delay. I will need for you to designate a track chair who will be my 
single point of contact for your track. You can handle communication 
with your project however you like, but I need one person that I can 
rely on to be that point of contact. That track chair should subscribe 
to plann...@apachecon.com in order to be included in all relevant 
conversations


I hope to have helpful documentation for track chairs, so you won’t be 
doing it all on your own.


I really hope to see your project at ApacheCon @Home 2020.

Rich Bowen
VP Conferences, The Apache Software Foundation

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

Re: [DISCUSS] Distribution guidelines for other platforms

2020-06-29 Thread Joey Frazee 

Justin this is great and I find myself searching mailing lists and INFRA and 
LEGAL JIRAs for past guidance like this.

A few nit-y suggestions:

- I think it’d be helpful to link out to the Nexus info [1].
- Maybe add a comment about who/how to get the ability to publish under the 
Docker Hub account.
- And, encouragement to follow the same signing and checksumming practice as 
for releases.

What do you think?

-joey

1. https://infra.apache.org/publishing-maven-artifacts.html

On Jun 28, 2020, 3:00 AM -0500, Justin Mclean , wrote:
Hi,

The name on Pipy could be https://pypi.org/project/apache- to
keep consistent with other platforms.

The name on NPM has the same issue.

As long as it clear it’s an Apache project (for releases made by the PPMC) then 
any similar variations is fine.

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-29 Thread Sheng Zha (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148108#comment-17148108
 ] 

Sheng Zha commented on INCUBATOR-253:
-

Here's an update on the progress so far. See live version in 
https://github.com/apache/incubator-mxnet/issues/18397

Per 
https://lists.apache.org/thread.html/r738c102492649c754f49e2195985bc765df07df3c8a1e06942e8872f%40%3Cdev.mxnet.apache.org%3E,
 there are several licensing issues that we need to address and below are the 
issues as well as action items in each area.

## Developer pre-releases

This section tracks the problems that are related to nightly builds and 
developer-only pre-releases. The related issues are:
- Developer releases available to users and public searchable 
https://repo.mxnet.io / https://dist.mxnet.io
- The repo.mxnet.io and dist.mxnet.io weren't clear that the binaries there are 
for developer testing only and not for public consumption.
 
**Actions**
- [x] Add disclaimer to repo.mxnet.io and dist.mxnet.io to clarify that the 
nightly releases there are not intended for public consumption. (**done**)
- [x] Remove non-Apache releases in github release page. 
(**done**)(https://github.com/apache/incubator-mxnet/releases)
- [x] Remove repo.mxnet.io and dist.mxnet.io from search engine index 
(**done**)(https://github.com/apache/incubator-mxnet/issues/18397#issuecomment-647075093)

## First-party release

This section tracks the problems that are related to official releases that are 
intended to be Apache License v2 compliant. The related issues are:
- convenance binary releases containing Category X licensed code
- Maven releases containing Category X licensed code.
- PiPy releases containing Category X licensed code.
- Docker releases containing Category X licensed code.
- Trademark and branding issues with PiPy and Docker releases.

**Actions**
- [ ] Delete problematic Maven releases. (**Waiting for action from Apache 
infra**) 
([thread](https://lists.apache.org/thread.html/ra4e9572ac74857a80c64a31e8bf292d353e74cfa87bf457f47450303%40%3Cdev.mxnet.apache.org%3E),
 [INFRA-20442](https://issues.apache.org/jira/browse/INFRA-20442))
- [ ] Delete problematic pypi releases.
- [ ] Delete problematic docker releases.

## Third-party release

This section tracks the problems that are related to convenience binary 
releases that cannot be Apache License v2 compliant. The related issues are:
- Lack of clarity on all platforms for what is an ASF release and what is not.
- Developer releases available to users and public searchable 
https://repo.mxnet.io / https://dist.mxnet.io
- Trademark and branding issues with PiPy and Docker releases.
- NVIDIA's build of MXNet contains unreleased code: 
https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html
- AWS Deep Learning Container build of MXNet contains unreleased code: 
https://github.com/aws/deep-learning-containers/blob/master/mxnet/training/docker/1.6.0/py3/Dockerfile.gpu#L10

**Actions**
- [ ] Review with Apache Trademark on the current third-party binary 
distributions of mxnet and make necessary correction. (**In progress**)
- [ ] Review with Apache Legal on the appropriate license for convenience 
binary distribution and display it prominently. (**in 
progress**)([LEGAL-515](https://issues.apache.org/jira/browse/LEGAL-515))
- [ ] Resolve NVIDIA trademark usage issue for MXNet (**in progress**, engaged 
NVIDIA in [LEGAL-516](https://issues.apache.org/jira/browse/LEGAL-516))
- [ ] Resolve Amazon trademark usage issue for MXNet (**in progress**)
- [ ] Replacement Maven binary release as third-party release.
- [ ] Replacement pypi binary releases as third-party release.

## Documentation

This section tracks the problems that are related to documentation for releases 
and pre-releases. The related issues are:
- Website giving access to downloads of non released/unapproved code.
- Website giving access to releases containing Category X licensed code.
- Web site doesn't given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
- Lack of clarity on all platforms for what is an ASF release and what is not.

**Actions**
- [ ] create separate Apache and non-Apache release sections in downloads page.
- [x] add disclaimer for non-Apache releases in installation selector (**done**)
- [x] remove mentions of nightly builds in pypi page in wheel build pipeline 
(**done**, update will happen with next release)

## Longer-term

This section tracks items that are for the purpose of mitigating usability 
impact as a result of addressing the issues above.

**Actions**
- [ ] Add source distribution to PyPI package `apache-mxnet` and build 
automatically on user machines.

Related:
#18463 
https://issues.apache.org/jira/browse/INCUBATOR-253

> Issues with MXNet releases and their distribution
> ---

[jira] [Issue Comment Deleted] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-29 Thread Justin Mclean (Jira) 


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Mclean updated INCUBATOR-253:

Comment: was deleted

(was: Here's an update on the progress so far. See live version in 
https://github.com/apache/incubator-mxnet/issues/18397

Per 
https://lists.apache.org/thread.html/r738c102492649c754f49e2195985bc765df07df3c8a1e06942e8872f%40%3Cdev.mxnet.apache.org%3E,
 there are several licensing issues that we need to address and below are the 
issues as well as action items in each area.

## Developer pre-releases

This section tracks the problems that are related to nightly builds and 
developer-only pre-releases. The related issues are:
- Developer releases available to users and public searchable 
https://repo.mxnet.io / https://dist.mxnet.io
- The repo.mxnet.io and dist.mxnet.io weren't clear that the binaries there are 
for developer testing only and not for public consumption.
 
**Actions**
- [x] Add disclaimer to repo.mxnet.io and dist.mxnet.io to clarify that the 
nightly releases there are not intended for public consumption. (**done**)
- [x] Remove non-Apache releases in github release page. 
(**done**)(https://github.com/apache/incubator-mxnet/releases)
- [x] Remove repo.mxnet.io and dist.mxnet.io from search engine index 
(**done**)(https://github.com/apache/incubator-mxnet/issues/18397#issuecomment-647075093)

## First-party release

This section tracks the problems that are related to official releases that are 
intended to be Apache License v2 compliant. The related issues are:
- convenance binary releases containing Category X licensed code
- Maven releases containing Category X licensed code.
- PiPy releases containing Category X licensed code.
- Docker releases containing Category X licensed code.
- Trademark and branding issues with PiPy and Docker releases.

**Actions**
- [ ] Delete problematic Maven releases. (**Waiting for action from Apache 
infra**) 
([thread](https://lists.apache.org/thread.html/ra4e9572ac74857a80c64a31e8bf292d353e74cfa87bf457f47450303%40%3Cdev.mxnet.apache.org%3E),
 [INFRA-20442](https://issues.apache.org/jira/browse/INFRA-20442))
- [ ] Delete problematic pypi releases.
- [ ] Delete problematic docker releases.

## Third-party release

This section tracks the problems that are related to convenience binary 
releases that cannot be Apache License v2 compliant. The related issues are:
- Lack of clarity on all platforms for what is an ASF release and what is not.
- Developer releases available to users and public searchable 
https://repo.mxnet.io / https://dist.mxnet.io
- Trademark and branding issues with PiPy and Docker releases.
- NVIDIA's build of MXNet contains unreleased code: 
https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html
- AWS Deep Learning Container build of MXNet contains unreleased code: 
https://github.com/aws/deep-learning-containers/blob/master/mxnet/training/docker/1.6.0/py3/Dockerfile.gpu#L10

**Actions**
- [ ] Review with Apache Trademark on the current third-party binary 
distributions of mxnet and make necessary correction. (**In progress**)
- [ ] Review with Apache Legal on the appropriate license for convenience 
binary distribution and display it prominently. (**in 
progress**)([LEGAL-515](https://issues.apache.org/jira/browse/LEGAL-515))
- [ ] Resolve NVIDIA trademark usage issue for MXNet (**in progress**, engaged 
NVIDIA in [LEGAL-516](https://issues.apache.org/jira/browse/LEGAL-516))
- [ ] Resolve Amazon trademark usage issue for MXNet (**in progress**)
- [ ] Replacement Maven binary release as third-party release.
- [ ] Replacement pypi binary releases as third-party release.

## Documentation

This section tracks the problems that are related to documentation for releases 
and pre-releases. The related issues are:
- Website giving access to downloads of non released/unapproved code.
- Website giving access to releases containing Category X licensed code.
- Web site doesn't given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
- Lack of clarity on all platforms for what is an ASF release and what is not.

**Actions**
- [ ] create separate Apache and non-Apache release sections in downloads page.
- [x] add disclaimer for non-Apache releases in installation selector (**done**)
- [x] remove mentions of nightly builds in pypi page in wheel build pipeline 
(**done**, update will happen with next release)

## Longer-term

This section tracks items that are for the purpose of mitigating usability 
impact as a result of addressing the issues above.

**Actions**
- [ ] Add source distribution to PyPI package `apache-mxnet` and build 
automatically on user machines.

Related:
#18463 
https://issues.apache.org/jira/browse/INCUBATOR-253)

> Issues with MXNet releases and their distribution
>

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-29 Thread Sheng Zha (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148199#comment-17148199
 ] 

Sheng Zha commented on INCUBATOR-253:
-

Justin, why did you delete my comment?

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-29 Thread Sheng Zha (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148199#comment-17148199
 ] 

Sheng Zha edited comment on INCUBATOR-253 at 6/29/20, 11:28 PM:


Justin, on what ground did you delete my comment? I believe anyone in Apache 
should be able to make any comments that are related to the topic as long as 
the conversation is civilized. So I find the deletion inappropriate and rude.

Link to the related conversation on why the updates are organized the way I was 
providing it: 
https://lists.apache.org/thread.html/r0446adfbbed24b016338b2cfa6dcef90066b203162e464ae0088da08%40%3Cprivate.mxnet.apache.org%3E


was (Author: zhasheng):
Justin, why did you delete my comment?

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: [DISCUSS] Distribution guidelines for other platforms

2020-06-29 Thread Brian Fox 
I independently noticed and added [1] so that's covered.

On Mon, Jun 29, 2020 at 12:06 PM Joey Frazee
 wrote:
>
> Justin this is great and I find myself searching mailing lists and INFRA and 
> LEGAL JIRAs for past guidance like this.
>
> A few nit-y suggestions:
>
> - I think it’d be helpful to link out to the Nexus info [1].
> - Maybe add a comment about who/how to get the ability to publish under the 
> Docker Hub account.
> - And, encouragement to follow the same signing and checksumming practice as 
> for releases.
>
> What do you think?
>
> -joey
>
> 1. https://infra.apache.org/publishing-maven-artifacts.html
>
> On Jun 28, 2020, 3:00 AM -0500, Justin Mclean , wrote:
>
> Hi,
>
> The name on Pipy could be https://pypi.org/project/apache- to
> keep consistent with other platforms.
>
> The name on NPM has the same issue.
>
>
> As long as it clear it’s an Apache project (for releases made by the PPMC) 
> then any similar variations is fine.
>
> Thanks,
> Justin
> -
> 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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-29 Thread Justin Mclean (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148268#comment-17148268
 ] 

Justin Mclean commented on INCUBATOR-253:
-

Please refer to the conversation on your private list.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[ANNOUNCE] Apache APISIX (incubating) 1.4 released

2020-06-29 Thread Nirojan Selvanathan 
Hi all,

The Apache APISIX (incubating) community is glad to announce that Apache
APISIX(incubating) 1.4 has been released!

Apache APISIX is a cloud-native microservices API gateway, delivering the
ultimate performance, security, open-source and scalable platform for all
your APIs and microservices.

Apache APISIX is based on Nginx and Etcd, it has dynamic routing
and plug-in hot loading, which is especially suitable for API management
under the micro-service system.

Download Link: http://www.apache.org/dist/incubator/apisix/

Release Note:
https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md

Website: http://apisix.apache.org/

APISIX Resources:
- issues: https://github.com/apache/incubator-apisix/issues
- Mailing-list: d...@apisix.apache.org

=
*Disclaimer*

Apache APISIX (incubating) is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by the Apache Incubator PMC.
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.

-- 
Best Regards,
S.Nirojan

Re: [ANNOUNCE] Apache APISIX (incubating) 1.4 released

2020-06-29 Thread tison 
congrats!

Best,
tison.


Nirojan Selvanathan  于2020年6月30日周二 上午11:13写道：

> Hi all,
>
> The Apache APISIX (incubating) community is glad to announce that Apache
> APISIX(incubating) 1.4 has been released!
>
> Apache APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security, open-source and scalable platform for all
> your APIs and microservices.
>
> Apache APISIX is based on Nginx and Etcd, it has dynamic routing
> and plug-in hot loading, which is especially suitable for API management
> under the micro-service system.
>
> Download Link: http://www.apache.org/dist/incubator/apisix/
>
> Release Note:
> https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md
>
> Website: http://apisix.apache.org/
>
> APISIX Resources:
> - issues: https://github.com/apache/incubator-apisix/issues
> - Mailing-list: d...@apisix.apache.org
>
> =
> *Disclaimer*
>
> Apache APISIX (incubating) is an effort undergoing incubation at The Apache
> Software Foundation (ASF), sponsored by the Apache Incubator PMC.
> 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.
>
> --
> Best Regards,
> S.Nirojan
>

Re: [ANNOUNCE] Apache APISIX (incubating) 1.4 released

2020-06-29 Thread YuanSheng Wang 
congratulations ^_^


On Tue, Jun 30, 2020 at 11:15 AM tison  wrote:

> congrats!
>
> Best,
> tison.
>
>
> Nirojan Selvanathan  于2020年6月30日周二 上午11:13写道：
>
> > Hi all,
> >
> > The Apache APISIX (incubating) community is glad to announce that Apache
> > APISIX(incubating) 1.4 has been released!
> >
> > Apache APISIX is a cloud-native microservices API gateway, delivering the
> > ultimate performance, security, open-source and scalable platform for all
> > your APIs and microservices.
> >
> > Apache APISIX is based on Nginx and Etcd, it has dynamic routing
> > and plug-in hot loading, which is especially suitable for API management
> > under the micro-service system.
> >
> > Download Link: http://www.apache.org/dist/incubator/apisix/
> >
> > Release Note:
> > https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md
> >
> > Website: http://apisix.apache.org/
> >
> > APISIX Resources:
> > - issues: https://github.com/apache/incubator-apisix/issues
> > - Mailing-list: d...@apisix.apache.org
> >
> > =
> > *Disclaimer*
> >
> > Apache APISIX (incubating) is an effort undergoing incubation at The
> Apache
> > Software Foundation (ASF), sponsored by the Apache Incubator PMC.
> > 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.
> >
> > --
> > Best Regards,
> > S.Nirojan
> >
>


-- 

*MembPhis*
My GitHub: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix