-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: release 2.0-rc version. #598
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
membphis
reviewed
Oct 24, 2020
juzhiyuan
requested changes
Oct 26, 2020
membphis
approved these changes
Oct 26, 2020
* feat: separate build and run * doc: update doc about build and run * doc: update doc about build and run * Update schema-sync.sh * Update develop.md * Update develop.zh-CN.md Co-authored-by: 琚致远 <juzhiyuan@apache.org>
juzhiyuan
approved these changes
Oct 26, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* doc: add etcd version tips(#602) * Update README.md * Update README.zh-CN.md Co-authored-by: 琚致远 <juzhiyuan@apache.org>
* fix: remove json schema generation from ci * fix: use json schema generated from APISIX v2.0
juzhiyuan
approved these changes
Oct 27, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Update CHANGELOG.md * Update CHANGELOG.zh-CN.md * docs: update change log Co-authored-by: nic-chen <johz@163.com>
* fix: consumer schema for auth plugin * fix: update by jsonschema * fix: json schema
* feat(doc): update README & deploy * feat(docs): added FAQ * fix: linkx * feat(docs): update deploy with docker * feat(docs): update FAQ * feat: update README * feat: update README * feta: update README * fix: link * feat: update deploy with docker * feat(docs): added tip for some users * feat(doc): improve deploy with docker * feat(docs): improve deploy with docker * feat(doc): update run with docker * feat(doc): improve deploy * feat(doc): added more info * feat(doc): added more info * feat(doc): remove extra info * feat: added more detailed * fix: CI fail according `api/conf/conf.yaml ` is changed. * fix: revert changed * feat(docs): improve English version * feat(docs): use frontend instead, just like backend * feat(docs): remove extra statements * feat(docs): update typo * feat(docs): remove startup with message * feat: update CI's name Co-authored-by: nic-chen <johz@163.com>
* ci: fix CI fail * ci: fix CI fail * ci: fix CI fail
juzhiyuan
approved these changes
Nov 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please answer these questions before submitting a pull request
Why submit this pull request?
Bugfix
New feature provided
Improve performance
Related issues
Bugfix
Description
How to fix?
New feature or improvement
This part will track all issues related to 2.0 RC3
api
#546