Front page | perl.perl5.porters |
Postings from February 2022
From: Neil Bowers
February 1, 2022 09:23
Message ID: 93530101-c5a5-4ab6-a482-99ae89a42ad6@Spark
The RFC process is documented in the RFCs repo, but it has evolved a bit as we've been running it, so we discussed a summary of it in the last meeting, and agreed that this is how we think things are/should-be running now.
• If you want to propose a change to the language, send an elevator pitch to p5p (see below)
• The proposal is discussed on p5p. The PSC keeps track of proposals, by looking for "Pre-RFC" threads.
• If the discussion doesn't kill it, and the PSC doesn't veto it, the PSC will ask you to submit a PR on the RFCs repo. They'll give you a number for the RFC.
• Submit a PR, based on the RFC template
• Discussion will continue on the PR, if there are any major issues / disagreements.
• The PSC will either merge or reject the PR. If merged, the Status: field will then track progress.
• Provisional: the what has been agreed, implementation details not nailed down
• Accepted: what and how agreed, awaiting implementation
• Implemented: is in blead
• Shipped/Experimental: has gone out in a stable release, with experimental cover
• Shipped/Stable: in stable release without experimental cover
Email sent to p5p with the subject line "Pre-RFC: [one-line summary]".
This should not be based on the RFC template, but should be 4 paragraphs:
1. problem statement
2. proposed change
4. potential problems
We’re expecting some discussion on this; when there's convergence, we'll update the RFCs repo.
by Neil Bowers