The current policy about the “Release Manager Selection” process is using unclear and confusing terminology and allows for decisions to be made that no longer match the currently practiced reality and leave room for ambiguity with regard to the interpretation of the voting results.
As an example, it specifies that “[t]he release manager team consists of two or three people” where “at least one […] should be a ‘veteran’” and “[t]he other can be […] a veteran, or […] someone new”. It is not clear how the decision between two or three RMs is to be made and what happens if a veteran receives fewer votes than “someone new”.
In practice the last several PHP versions always had 3 RMs, with the veteran RM being one of the RMs of the previous PHP version and not actively participating in the “daily business” and two “rookie” RMs who were provided advice by the veteran. The “call for applications” usually also specifically mentioned a 1 veteran + 2 rookie split, which added to confusion as to how the voting should be set up when multiple applicants qualified for the veteran role.
This policy RFC intents to clarify the process by using clearer terminology and removing “alternatives”.
Accept the policy in https://github.com/php/policies/pull/28.
To summarize the policy from a high-level perspective, the policy specifies:
The policy aims to match the “current working practice” of the RM selection in the past several years.
None.
None.
Primary Vote requiring a 2/3 majority to accept the RFC:
After the RFC is implemented, this section should contain:
None.