Hi all, Can we discuss the policy for major and minor release management?
The current approach using milestone for tracking how a pull request is merged is a bit confusing. For example, I am seeing some issues labelled as 2.3.1 but the pull requests are created based on master. I don't know how I should merge this pull request. Because the change effectively will be merged into master and released as 2.4.0 release, unless someone is cherry-picking the change to branch-2.3. The disconnection between merges and release management is kind of confusing me when merging the pull requests. I am kind of always hesitate to merge such pull requests. I was proposing using what BookKeeper is using for managing major and minor releases and having a merge script to handle labelling and cherry-picks. But the proposal was not in the favor of pulsar community. Can anyone propose a change to current release management? Otherwise it is not a scalable solution because not every committer knows how to handle this situation clearly. Thanks, Sijie
