PengHui, There is a recent discussion with Matteo (at the community meetings) about preparing the release branch a couple of weeks before sending out the official VOTE.
What about creating the branch-2.10 as soon as possible? We will commit to that branch only the fixes needed to make 2.10.0 stable This way we will be free to commit new stuff to master branch without impacting the stability of 2.10 This way people can start validating 2.10 seriously in order to catch problems before sending out the RC Does it sound like a good idea to you ? Enrico Il giorno mer 9 feb 2022 alle ore 09:25 PengHui Li <peng...@apache.org> ha scritto: > > Hi all, > > Sorry for the late reply, due to my vacation these days, we got a delay > here. > > Most of the changes of 2.10.0 are getting merged, for now, there are 14 > opened PRs(10 approved) > https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.10.0 > > I will take care of them and try to get them merged. > After the above PRs get merged, I will build the release and start the vote. > Please let me know if you have any questions about the 2.10.0 release. > And, also looking forward to more people taking a look at the opened PRs. > > Regards, > Penghui > > > > > On Tue, Jan 4, 2022 at 7:56 AM Sijie Guo <guosi...@gmail.com> wrote: > > > +1. > > > > All make sense to me! > > > > We probably need to move to the feature frozen stage in order to cut a > > release at the end of January. > > > > - Sijie > > > > On Sun, Dec 26, 2021 at 8:46 PM PengHui Li <peng...@apache.org> wrote: > > > > > Hi, everyone > > > > > > I hope you’ve all been doing well. I would like to start an email thread > > to > > > discuss features that we planned for 2.10.0. > > > According to the time-based release plan > > > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan, > > > we should release 2.10.0 at the end of December 2021, since we have > > reached > > > the end of December, > > > I would like to target the 2.10.0 to the end of January 2022 > > > > > > There are some powerful features and enhancements in 2.10.0 such as > > > > > > - PIP 84: Message redelivery epoch > > > - PIP 104: Add new consumer type: TableView > > > - PIP 106: Negative acknowledgment backoff > > > - PIP 110: Topic customized metadata support > > > - PIP 117: Change Pulsar standalone defaults > > > - PIP 118: Do not restart brokers when ZooKeeper session expires > > > - PIP 119: Enable consistent hashing by default on KeyShared dispatcher > > > - PIP 120: Enable client memory limit by default > > > - PIP 121: Pulsar cluster level auto failover > > > - PIP 123: Pulsar metadata CLI tool > > > - Metadata service batch operations > > > - RocksDB metadata service backend > > > - Etcd metadata service backend > > > - Ack timeout redelivery backoff policy > > > - Global topic policies > > > > > > Most of them have been completed, some work in progress we need to try to > > > complete within 2 weeks. > > > This can give me a 2 week buffer period to prepare for release and > > complete > > > the release vote. > > > For the unfinished parts, we can move them to 2.11.0. > > > > > > Some proposals are just being discussed, so I do not list them because > > I'm > > > not sure if we can complete them in two weeks. > > > > > > You can find all the change lists from > > > > > > > > https://github.com/apache/pulsar/pulls?q=milestone%3A2.10.0+-label%3Arelease%2F2.9.1 > > > There are more than 500 commits. > > > > > > If I missed something or you have any suggestions please let me know. > > > > > > Regards, > > > Penghui > > > > >
