Hello Enrico: I am releasing 2.8.2, and I wrote a small tool to help me generate the 2.8.2 release notes, I found that I need several tags to identify: 1) Component, used to identify which type of PR this PR belongs to. I think we can discuss which components to keep in the future. There are a lot of components now 2) cherry-picked/branch-2.8 and release/2.8.2, `release/2.8.2` is used to identify whether the current release, `cherry-picked/branch-2.8` is used to identify whether I need to generate documentation for this PR
Lin Lin On 2021/12/02 11:11:43 Enrico Olivelli wrote: > Hello community, > > There is an open discussion on the Pulsar 2.9.0 release notes PR: > https://github.com/apache/pulsar/pull/12425 > > I have created the block of release notes by downloading the list of PR > using some GitHub API. > Then I have manually classified: > - News and Noteworthy: cool things in the Release > - Breaking Changes: things you MUST know when you upgrade > - Java Client, C++ Client, Python Client, Functions/Pulsar IO > > The goal is to provide useful information for people who want to upgrade > Pulsar. > > My problems are: > - PR titles are often badly written, but I don't want to fix all of them > (typos, tenses of verbs, formatting) > - There are more than 300 PRs, I don't want to classify them manually, I > just highlighted the most important from my point of view > > If for 2.9.0 we still keep a list of PR, then I believe that the current > status of the patch is good. > > If we want to do it another way, then I am now asking if there is someone > who can volunteer in fixing and classifying the list of 300 PRs, it is a > huge task. > > There is already much more work to do to get 2.9.0 completely released (and > also PulsarAdapters) and we have to cut 2.9.1 as soon as possible due to a > bad regression found in 2.9.0. > > Thanks > Enrico >
