Skip to content

Remove master from the docs site version config.#7874

Merged
creachadair merged 1 commit intomasterfrom
mjf/no-master-docs
Feb 21, 2022
Merged

Remove master from the docs site version config.#7874
creachadair merged 1 commit intomasterfrom
mjf/no-master-docs

Conversation

@creachadair
Copy link

@creachadair creachadair commented Feb 18, 2022

We might want to do this for v0.33 also.

Per the below we'll keep v0.33 for now.

@creachadair creachadair force-pushed the mjf/no-master-docs branch 2 times, most recently from b22e8a5 to cbcb04b Compare February 18, 2022 18:26
@creachadair
Copy link
Author

Going to hold this till after #7870 and #7871 so that we get the link updates in the versions as well.

@creachadair creachadair force-pushed the mjf/no-master-docs branch 7 times, most recently from 1b35816 to db7427e Compare February 19, 2022 21:10
@creachadair creachadair force-pushed the mjf/no-master-docs branch 2 times, most recently from fc7fbca to 9f6150e Compare February 20, 2022 19:37
Copy link
Contributor

@cmwaters cmwaters left a comment

Choose a reason for hiding this comment

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

I would keep v0.33 for now. I think we should keep docs around for 1 or 2 more versions than what we promise to actively maintain.

@cmwaters
Copy link
Contributor

The interesting thing is that we need to remove master on all the backported branches as well :)

@cmwaters cmwaters added S:backport-to-v0.34.x Tell mergify to backport the PR to v0.34.x S:backport-to-v0.35.x labels Feb 21, 2022
@creachadair
Copy link
Author

The interesting thing is that we need to remove master on all the backported branches as well :)

Yup. To v0.33 also, but that one will have to be manual as it predates our automation. 🙂

@cmwaters
Copy link
Contributor

I've also noticed that the backported branches still reference v0.32 as well

@creachadair
Copy link
Author

I've also noticed that the backported branches still reference v0.32 as well

Yeah, I'll do a cleanup pass on all of them.

@creachadair creachadair merged commit 351adf8 into master Feb 21, 2022
@creachadair creachadair deleted the mjf/no-master-docs branch February 21, 2022 14:07
mergify bot pushed a commit that referenced this pull request Feb 21, 2022
(cherry picked from commit 351adf8)

# Conflicts:
#	docs/.vuepress/config.js
#	docs/versions
mergify bot pushed a commit that referenced this pull request Feb 21, 2022
(cherry picked from commit 351adf8)

# Conflicts:
#	docs/versions
creachadair pushed a commit that referenced this pull request Feb 21, 2022
)

* Remove master from the docs site version config. (#7874)

(cherry picked from commit 351adf8)

Co-authored-by: M. J. Fromberger <fromberger@interchain.io>
creachadair pushed a commit that referenced this pull request Feb 21, 2022
)

* Remove master from the docs site version config. (#7874)

(cherry picked from commit 351adf8)

Co-authored-by: M. J. Fromberger <fromberger@interchain.io>
creachadair pushed a commit that referenced this pull request Feb 21, 2022
creachadair pushed a commit that referenced this pull request Feb 21, 2022
@creachadair
Copy link
Author

It appears a lot of the search results on Google point directly to master for whatever reason. I think we ought to probably set up a redirect from master to the latest release (v0.35) on the generated site, so that those links at least go somewhere relevant instead of 404.

lklimek referenced this pull request in dashpay/tenderdash Apr 1, 2022
…903)

* Remove master from the docs site version config. (#7874)

(cherry picked from commit 351adf8)

Co-authored-by: M. J. Fromberger <fromberger@interchain.io>
(cherry picked from commit 8c24914)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S:backport-to-v0.34.x Tell mergify to backport the PR to v0.34.x

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants