Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I submitted the PR https://github.com/apache/pulsar-site/pull/843 Best, Kiryl > On Mar 10, 2024, at 10:02 PM, Kiryl Valkovich wrote: > > Asaf and Dave, thank you for your responses. > > The proposed version menu structure looks good to me: > - Next > - active versions still in support > - O

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

Asaf and Dave, thank you for your responses. The proposed version menu structure looks good to me: - Next - active versions still in support - Others If there will be no more input, I’m going to submit the PR in the upcoming week. I updated the redirect and the release process instructions. Pl

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I like the notion of not updating documentation for versions that are out of EOL unless the documentation is incorrect. The only versions that should be on the documentation pop-up on https:/pulsar.apache.org/docs/x,y,z/ should be: - Next - active versions

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I personally agree it is frustrating to update in multiple places. It's not time consuming, just annoying. Maybe we can only update for the support LTS version and onwards? On Mar 6 2024, at 1:56 pm, Kiryl Valkovich wrote: > Idea: don't require updating versioned docs from contributors. > Making

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

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 h