This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 3b075a60f04 [improve][doc] Clarify where to grab the number for the
PIP (#19610)
3b075a60f04 is described below
commit 3b075a60f04938fa1a90acc2fd856168ca0cadef
Author: Asaf Mesika <[email protected]>
AuthorDate: Fri Feb 24 02:15:15 2023 +0200
[improve][doc] Clarify where to grab the number for the PIP (#19610)
---
wiki/proposals/PIP.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/wiki/proposals/PIP.md b/wiki/proposals/PIP.md
index d972956df02..f76c9f0f7a2 100644
--- a/wiki/proposals/PIP.md
+++ b/wiki/proposals/PIP.md
@@ -78,7 +78,9 @@ A PIP proposal can be in these states:
The process works in the following way:
1. The author(s) of the proposal will create a GitHub issue ticket choosing the
- template for PIP proposals.
+ template for PIP proposals. The issue title should be "PIP-xxx: title",
where
+ the "xxx" number should be chosen to be the next number from the existing
PIP
+ issues, listed [here]([url](https://github.com/apache/pulsar/labels/PIP)).
2. The author(s) will send a note to the [email protected] mailing list
to start the discussion, using subject prefix `[DISCUSS] PIP-xxx: `. The
discussion
need to happen in the mailing list. Please avoid discussing it using
@@ -89,12 +91,12 @@ The process works in the following way:
4. Once some consensus is reached, there will be a vote to formally approve
the proposal.
The vote will be held on the [email protected] mailing list. Everyone
- is welcome to vote on the proposal, though it will considered to be binding
+ is welcome to vote on the proposal, though it will be considered to be
binding
only the vote of PMC members.
I would be required to have a lazy majority of at least 3 binding +1s votes.
The vote should stay open for at least 48 hours.
5. When the vote is closed, if the outcome is positive, the state of the
- proposal is updated and the Pull Requests associated with this proposal can
+ proposal is updated, and the Pull Requests associated with this proposal can
start to get merged into the master branch.
All the Pull Requests that are created, should always reference the
