Skip to content

Commit 020ebcb

Browse files
committedFeb 7, 2024
Merged pull request #3
2 parents 356e62f + 4184902 commit 020ebcb

File tree

1 file changed

+26
-27
lines changed

1 file changed

+26
-27
lines changed
 

‎release-process.rst

+26-27
Original file line numberDiff line numberDiff line change
@@ -172,33 +172,32 @@ the bug tracker)
172172
Release managers selection
173173
~~~~~~~~~~~~~~~~~~~~~~~~~~
174174

175-
The release managers team should be selected in a more transparent way. The
176-
ideal way is again to go through a proposal and a vote. The same system than
177-
the RFCs can obviously be used for the release managers selection.
178-
179-
The volunteers (a team of two persons) can add propose themselves via the
180-
mailing list and they will be added to a RFC page. A week between the last
181-
call and the vote should be sufficient (given that anyone can volunteer
182-
himself for the next release at any time). The vote takes place for a week.
183-
184-
Examples:
185-
186-
- John/Fred (yes, no)
187-
- Ted/Georges (yes, no)
188-
- Leon/Nikita (yes, no)
189-
190-
The team with the most votes will be then the RMs for the given release. One
191-
person cannot be a RM for more than one release at the same time.
192-
193-
Again, one of the questions for this section is about who will be allowed to
194-
vote:
195-
196-
- php-src (yes, no)
197-
- php-doc (yes, no)
198-
- qa, phpt (yes, no)
199-
- other sub projects like pear (yes, no)
200-
201-
NB: the poll plugin will be installed shortly
175+
About three months prior to the scheduled release of the first alpha release
176+
of the next minor or major version (around March 1st or shortly thereafter),
177+
the release managers for the latest version branch should issue a call for
178+
volunteers to begin the selection process for the next release managers.
179+
180+
The release manager team consists of two or three people, it is notable that
181+
at least one of the volunteers should be a "veteran" release manager, meaning
182+
they have contributed to at least one PHP release in the past. The other can
183+
be an additional veteran or, ideally, someone new to the RM role (to increase
184+
number of veteran RMs).
185+
186+
Issue the call for volunteers on internals@lists.php.net on or around March
187+
1st. See, for example: https://news-web.php.net/php.internals/113334
188+
189+
There is no rule for how long the call for volunteers must remain open. We
190+
should aim to select the release managers by early April, so announcing the
191+
call in early March gives people about a month to decide whether they wish to
192+
volunteer.
193+
194+
Voting is conducted using "Single Transferrable Vote" (STV).
195+
196+
Using some maths, we'll start with the 1st preference and gradually remove
197+
candidates with the fewest votes, transferring votes that had previously gone
198+
to them to their voter’s 2nd preference, and so on. Once required number of
199+
candidates have a quorum (Droop quota), those will be officially selected as
200+
our RMs.
202201

203202
Feature(s) preview release, solving the experimental features
204203
-------------------------------------------------------------

0 commit comments

Comments
 (0)
Please sign in to comment.