v3.5 Documentation

[nate-double-u]

This issue collects the documentation activities that need to be done to support the v3.5 docs.

Docs release:

• Create v3.5 docs from /docs/next. Two options: either rename next to v3.5 (as suggested in the comment below), or copy it (not @chalin's preferred choice)
• Ensure latest refers to v3.5 Preparing site for v3.5 release #379
• Decide what next will refer to - for now, v3.5 (NW) Preparing site for v3.5 release #379
• Change v3.5-DRAFT to v3.5 Change v3.5-DRAFT to v3.5 #377
• Update git_version_tag in v3.5 _index.md front-matter Preparing site for v3.5 release #379

Additions (v3.5-specific):

• Blog post announcing the release - content/en/blog/2021: add "Announcing etcd 3.5" #312, v3.5 blog copyedits for opening paragraphs #331, Publish v3.5 release announcement #376, Preparing site for v3.5 release #379
  (set draft status to false and set correct date)
• Add initial docs for experimental distributed tracing feature [3.5] Add initial docs for experimental distributed tracing feature  #280, content/en/docs/next/op-guide/monitoring.md: Add distributed tracing #373
• Add etcdutl documentation Add etcdutl documentation #309

Updates (v3.5-specific):

• Update API reference docs (/content/en/docs/next/dev-guide/: api_concurrency_reference_v3.md & api_reference_v3.md) using etcd-io/etcd/scripts/genproto.sh. backport to v3.5: scripts/genproto.sh: updates needed etcd#13080. Update generated API references on v3.5 release #380

Related issues: #322 (which contains a long list to other related issues).

[chalin]

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.

[lilic]

Could we also add moving all metrics, logs, etc under a new section just for Observability in the navigation as per suggestion in the #280 (comment). What do you think?

[nate-double-u]

@lilic, I think having a separate section for Observability in the navigation is a good idea. I'll open a separate issue (#374) so We can discuss where it should fit, and what needs to be moved into it in issue #267. This would just be for next/v3.5 and onward correct?

[edited to point to a better issue]

[nate-double-u]

Sorry for the noise, New IA implementation #267 is probably a better place to discuss adding a new page/section for Observability.

[spzala]

@nate-double-u just fyi, I think we can take care of #377 under here. Thanks!

[nate-double-u]

Closing this issue as the remaining part of it (Adding etcdutl documentation #309) can be handled as a standalone issue -- congrats on the release everyone.