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

v3.5 docs prep: rename next to v3.5 #332

Closed
chalin opened this issue May 27, 2021 · 1 comment · Fixed by #363
Closed

v3.5 docs prep: rename next to v3.5 #332

chalin opened this issue May 27, 2021 · 1 comment · Fixed by #363
Assignees
Labels
e1-hours Effort: < 8 hrs in progress Indicates that an Issue is actively being worked on. p1-high p2-medium

Comments

@chalin
Copy link
Contributor

chalin commented May 27, 2021

From #328 (comment):

I'd like to propose the following strategy, at least until we decide whether #252 will be addressed or not:

  1. Rename /docs/next to /docs/v3.5
  2. Add a redirect rule from next to v3.5 (and remove the opposite redirect rule that was added via Prepare for v3.5 docs -- add a redirect link #326)
  3. NOT create another /docs/next folder until we have a need for it and/or until we've resolved what we'll be doing with Use only real version names, not next, for doc version subdirectories under /content #252, among other issues.

Originally posted by @chalin in #328 (comment)

@chalin
Copy link
Contributor Author

chalin commented May 28, 2021

It occurred to me that this might cause trouble/break the versions menu, but hopefully not. We might need to address #322 earlier.

@nate-double-u nate-double-u added the in progress Indicates that an Issue is actively being worked on. label Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e1-hours Effort: < 8 hrs in progress Indicates that an Issue is actively being worked on. p1-high p2-medium
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants