> Add necessary explanations, such as time-based release plan, release > frequency, semantic versioning, maintenance life cycle, etc.
I support adding the release dates and support dates to the downloads page. This makes it clear which downloads are supported and for how long. I am happy to submit the PR to move this information from the "Versioning Policy" page to the downloads page. Which doc's do I need to update in order to move this table? (This relates to my other thread asking about where to put this information, and because of the in-flight website changes, I am confused about where to contribute this update.) Further, I think we should move unsupported versions to another downloads page to make it even more obvious what is currently supported. In reviewing the PIP 148 sheet, I think that the versioning policy and the time based release plan could be too long for the downloads page. I propose that we have a dedicated page for this information and link to that page from the downloads page. I have actually been planning to contribute a "Release Plan" page to our website, so if you direct me where I should add it, I can convert PIP 47 into a page on the website. (Note that PIP 47 needs to be modified and should not be directly translated to the website, which is why I would like to drive the effort to get it onto our website. I will start a separate thread on the ML to discuss our release process moving forward once I know where to put this page on the website.) > Recently, we got some negative feedback from users. Are you able to provide a reference to the source of this feedback? Thanks! Michael On Mon, Mar 7, 2022 at 10:18 PM Yu <li...@apache.org> wrote: > > Thanks Li Li, for always helping in making breaking changes to Pulsar! > > On Tue, Mar 8, 2022 at 11:01 AM Li Li <urf...@apache.org> wrote: > > > +1, I will do this task. > > > > Li Li > > > > > On Mar 8, 2022, at 8:39 AM, Huanli Meng <hua...@streamnative.io.INVALID> > > wrote: > > > > > > +1 > > > > > > BR//Huanli > > > > > >> On Mar 8, 2022, at 3:52 AM, Sijie Guo <guosi...@gmail.com> wrote: > > >> > > >> Yu, thank you for driving this effort! Great to see a proposal focusing > > on this! +1 > > >> > > >> On Fri, Mar 4, 2022 at 2:59 AM Yu <li...@apache.org <mailto: > > li...@apache.org>> wrote: > > >> Hi Pulsarers, > > >> > > >> For Pulsar release notes [1], we had issues below for a long time. > > >> > > >> - All contents are on a single Pulsar release note page. No > > navigations. It's easy to get lost and hard to understand which changes > > belong to which Pulsar version. > > >> - Java, C++, Python, WebSocket clients do not have independent release > > notes, they belong to parts of Pulsar release notes. It is hard to find and > > use. > > >> - Go, Node.js, C# clients’ changelogs are hosted in their own GitHub > > repos and not shown on the Pulsar website. Users need more clicks to get > > the info. > > >> - ... > > >> > > >> Recently, we got some negative feedback from users. I've submitted some > > changes [2] but it's a stopgap. > > >> > > >> To completely solve these problems, I propose to make some changes in > > PIP 148 [3], including but not limited to: > > >> > > >> - Create a "Release notes" chapter to docs, which shows all releases > > changes and release timeline. > > >> - Add necessary explanations, such as time-based release plan, release > > frequency, semantic versioning, maintenance life cycle, etc. > > >> - Create independent release notes for all clients. > > >> - Automate the process of generating all release notes, which is > > relevant to PIP 112 [4]. > > >> - Add navigations, etc. > > >> - ... > > >> > > >> > > >> Here are mockups [5]. You can check and comment without login. > > >> > > >> ACTION: Please provide your feedback within 72 hours. **If there is no > > discussion or objection, we’ll implement them as shown in the mockups.** > > >> > > >> We’d love your feedback! Thanks! > > >> > > >> [1] https://pulsar.apache.org/en/release-notes/ < > > https://pulsar.apache.org/en/release-notes/> > > >> [2] https://github.com/apache/pulsar/pull/14430 < > > https://github.com/apache/pulsar/pull/14430> > > >> [3] > > https://docs.google.com/document/d/1o6MWV3GvXQgKw1ZpL86y43xjnYvaUKrl6HxJKZnQyEU/edit#heading=h.35s8x8c7ja4c > > < > > https://docs.google.com/document/d/1o6MWV3GvXQgKw1ZpL86y43xjnYvaUKrl6HxJKZnQyEU/edit#heading=h.35s8x8c7ja4c> > > > > >> [4] > > https://docs.google.com/document/d/1Ul2qIChDe8QDlDwJBICq1VviYZhdk1djKJJC5wXAGsI/edit# > > < > > https://docs.google.com/document/d/1Ul2qIChDe8QDlDwJBICq1VviYZhdk1djKJJC5wXAGsI/edit# > > > > > >> [5] > > https://docs.google.com/spreadsheets/d/1MT8vt0620Cy4tggKk3gDVPbnhH7GVakld-5aDYCGAko/edit#gid=0 > > < > > https://docs.google.com/spreadsheets/d/1MT8vt0620Cy4tggKk3gDVPbnhH7GVakld-5aDYCGAko/edit#gid=0 > > > > > >> > > > > > > >
