Hi Enrico, I think we should cherry-pick the bug fixes, enhancements and test improvements? Only the new features and document should not cherry-pick release branch.
And, do you see any issues introduced in release branch from the cherry-picking? Thanks, Penghui On Nov 22, 2021, 5:38 PM +0800, Enrico Olivelli <eolive...@gmail.com>, wrote: > Hello, > I believe that we should not cherry-pick changes to released branches > (branch-2.x) if there is no strong reason to do it. > > I think that the only types of fixes that are eligible for cherry-picks are: > - security issues > - fixes for regressions > - fixes for serious bugs (but the change is not likely to break other > things or it does not need dependencies) > > Pulsar is widely used and any patch you add may make the branch unstable. > New features or improvements should go only to the "master" branch. > > We do not cut releases very often, and it is better to have stable branches. > > We do not have strong quality assurance systems against the branches that > are not the "master" branch, > so it is very hard to say that a released branch is stable. > > Thoughts ? > > Enrico
