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

[Doc] Clarify the relation between supported Pulsar versions and versioned docs #22177

Closed
1 of 2 tasks
visortelle opened this issue Mar 2, 2024 · 2 comments
Closed
1 of 2 tasks
Labels
doc-required Your PR changes impact docs and you will update later.

Comments

@visortelle
Copy link
Member

visortelle commented Mar 2, 2024

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

The release policy page states that Pulsar has two supported versions on the current date.

https://pulsar.apache.org/contribute/release-policy/#supported-versions
Screenshot 2024-03-03 at 12 57 11 AM

The documentation site provides four versions to choose from in the dropdown list:

Screenshot 2024-03-03 at 12 58 15 AM

This document describes that versioned docs also should be updated: https://pulsar.apache.org/contribute/document-contribution/#update-versioned-docs.

The "If you want to update versioned docs" statement is a bit vague. Let's say I found a mistake in the latest Pulsar version docs and want to fix it because I use this version. But I don't care about older versions. Therefore I "don't want" to update old versions, although probably should.

Also, this document doesn't clarify which versions should be updated - listed as actively supported on the release policy page or listed in the dropdown.

If some of them aren't actively supported, should they also be updated?

For example, Kubernetes maintains only the newest versions, although it's a cheat because they don't have an LTS version.

Maybe it also makes sense to maintain only versions that have the Active Support status, and for others to show a similar banner:

Screenshot 2024-03-04 at 12 59 26 AM

After figuring it out, I plan to update the page that describes the versioned docs update process a add it to the PULL_REQUEST_TEMPLATE.md checklist. Now the need to update versioned docs may be not clear for new contributors.

What is your suggestion?

Any reference?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@visortelle visortelle added the doc-required Your PR changes impact docs and you will update later. label Mar 2, 2024
@visortelle
Copy link
Member Author

visortelle commented Mar 6, 2024

Idea: don't require updating versioned docs from contributors.

Making a small documentation fix in a single place is easy, but if we ask contributors to fix it in 5-10 places, it may prevent the initiative at all.

It could increase the amount of contributions to the documentation.

I'm not sure how to better organize this process. Who should do this job - the PR reviewer or someone else like a technical writer?

@visortelle
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-required Your PR changes impact docs and you will update later.
Projects
None yet
Development

No branches or pull requests

1 participant