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

Dev Version Getting Started Mentions Previous Major Release #1462

Open
mattlord opened this issue May 9, 2023 · 5 comments
Open

Dev Version Getting Started Mentions Previous Major Release #1462

mattlord opened this issue May 9, 2023 · 5 comments

Comments

@mattlord
Copy link
Collaborator

mattlord commented May 9, 2023

Today the Vitess Development Version is 17.0. And in the getting started local install docs, installing vitess section, we mention the previous major release of 16.0: https://vitess.io/docs/17.0/get-started/local/#install-vitess

For the current development version we should instead link to building vitess from source using the vitessio/vitess main branch.

@mattlord mattlord self-assigned this May 9, 2023
@J0SAL
Copy link
Contributor

J0SAL commented May 15, 2023

Hey @mattlord , I would like to work on the issue, could you assign this to me

@mattlord
Copy link
Collaborator Author

Hi @J0SAL !

You can always open a PR w/o being assigned to the issue. I'll un-assign myself.

Thanks!

@mattlord mattlord removed their assignment May 17, 2023
@J0SAL
Copy link
Contributor

J0SAL commented May 19, 2023

Hi @mattlord,

can we just update the installation guidelines with this link https://vitess.io/docs/contributing/build-on-ubuntu/#build-vitess as it already mentions building vitess from source using the vitessio/vitess main branch.

@mattlord
Copy link
Collaborator Author

can we just update the installation guidelines with this link https://vitess.io/docs/contributing/build-on-ubuntu/#build-vitess as it already mentions building vitess from source using the vitessio/vitess main branch.

That's definitely one option. It might be the one we use in the end, but I wanted to see if there might be a better one first.

@J0SAL
Copy link
Contributor

J0SAL commented May 19, 2023

Hi @mattlord.
Can you provide you feedback on the PR #1476

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 a pull request may close this issue.

2 participants