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? Best, Kiryl > On Mar 5, 2024, at 12:15 AM, Kiryl Valkovich <visorte...@gmail.com> wrote: > > The release policy page states that Pulsar has two supported versions on the > current date. > The documentation site provides four versions to choose from in the dropdown > list. If some of them aren't actively supported, should they also be updated? > > GitHub issue with more details and screenshots: > https://github.com/apache/pulsar/issues/22177 > > > Best, > Kiryl
