> Adopting a plan from other popular projects like Kafka and Flink is a good starting point! Can you add the PIP to pulsar wiki page?
Sure, thanks Sijie work for this, will add the PIP to pulsar wiki page. > 在 2019年10月28日，下午8:56，Sijie Guo <guosi...@gmail.com> 写道： > > Xiaolong, > > Thank you for putting this together! This has been in my mind for a while. > We should a solid plan for release management since the community is now > growing really fast. > Adopting a plan from other popular projects like Kafka and Flink is a good > starting point! Can you add the PIP to pulsar wiki page? > > - Sijie > > On Mon, Oct 28, 2019 at 5:21 PM xiaolong ran <ranxiaolong...@gmail.com > <mailto:ranxiaolong...@gmail.com>> > wrote: > >> Hi all committers: >> >> It has been more than two months since the 2.4.1 release. But we don't >> have an accurate time about when we release the next version. We can only >> choose to extend the 2.4.2 Milestone. >> >> I am thinking of changing the release plan/schedule to a more time-based >> mechanism what other projects (like Kafka, Flink, Bookkeeper) are doing: >> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan >> <https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan> >> <https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan >> <https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan> >>> >> >> Some of the benefits are documented in their wikis (also copied them in >> the email for easy to read). >> >> 1. A quicker feedback cycle and users can benefit from features shipped >> quicker >> 2. Predictability for contributors and users: >> a. Developers and reviewers can decide in advance what release they >> are aiming for with specific features. >> b. If a feature misses a release we have a good idea of when it will >> show up. >> c. Users know when to expect their features >> 3. Transparency - There will be a published cut-off date (AKA feature >> freeze) for the release and people will know about it in advance. Hopefully >> this will remove the contention around which features make it. >> 4. Quality - we've seen issues pop up in release candidates due to >> last-minute features that didn't have proper time to bake in. More time >> between feature freeze and release will let us test more, document more and >> resolve more issues. >> >> The contents of the PIP are as follows: >> >> https://gist.github.com/wolfstudy/5a06d7b4bc27ac0d232ec6673f10aa0c < >> https://gist.github.com/wolfstudy/5a06d7b4bc27ac0d232ec6673f10aa0c >> <https://gist.github.com/wolfstudy/5a06d7b4bc27ac0d232ec6673f10aa0c>>
