Skip to content
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

PS-5427 Document the correct distribution upgrade process for Percona… #3324

Merged
merged 2 commits into from
Sep 13, 2019

Conversation

patrickbirch
Copy link
Contributor

… Server

Added the process to upgrade the distribution in-place with Percona Server already installed - 5.7

@laurynas-biveinis laurynas-biveinis changed the base branch from 8.0 to 5.7 July 22, 2019 11:05
@laurynas-biveinis
Copy link
Contributor

(changed the base branch from 8.0 to 5.7)

Copy link
Contributor

@laurynas-biveinis laurynas-biveinis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If 5.6 PR followed GCA, this one does not: there is only one commit, so there is no merge from 5.6

@patrickbirch
Copy link
Contributor Author

i will fix. thanks

@patrickbirch
Copy link
Contributor Author

I have merged with 5.6 and updated the 5.7 upgrading doc. It still comes out as one commit for two files. Is that correct, or should I commit them separately? Thanks.

@laurynas-biveinis
Copy link
Contributor

This is not a GCA process, please check the Confluence

@patrickbirch
Copy link
Contributor Author

Thanks. I will double-check and see what I missed.

@patrickbirch patrickbirch force-pushed the PS-5.7-5427 branch 6 times, most recently from 6bc526c to 7d58759 Compare July 29, 2019 14:09
Copy link
Contributor

@dutow dutow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For GCA pull requests, please wait until all versions are reviewed , and merge them together.

Will there be an 8.0 version? If yes, that needs a PR too. If no, it needs a null merge PR.

…cona Server - 5.7

Merged with 5.6 version
Added the distribution process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants