michaeljmarshall opened a new pull request #14647: URL: https://github.com/apache/pulsar/pull/14647
### Motivation In recent Pulsar community meetings, we have discussed updating the way that we practice the Pulsar Release Plan. @merlimat initially proposed modifying our plan by suggesting that we implement a code freeze to improve stability of new release branches. (This is a documented part of PIP 47, but it has not been followed. The suggestion is to follow that guidance.) Please feel free to leave comments about how (or if) we should update the Release Plan. ### Modifications * Copied the body of PIP 47 and pasted it here https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan * Made some minor grammatical fixes ### Method I am creating this PR to facilitate discussion, collaboration, and hopefully consensus about what our release process should look like. Note: I will leave my own review with suggested edits and questions for the PIP 47 release plan. I think this could be a valuable way to generate discussion around how we should improve our release plan. ### Verifying this change This change will need to be verified by the community. I will post a message to the mailing list to start this discussion. ### Does this pull request potentially affect one of the following parts: This is a process change. ### Documentation - [x] `doc` I am adding docs. If possible, I'd prefer to focus on the content of the release plan before worrying about the doc location on the website. It's important that we solidify our release plan, and I worry that it might be distracting to answer too many questions at once. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
