|
|
@@ -380,9 +380,12 @@ The review manager is responsible for validating that the proposal is ready for
|
|
|
the reviewing team to make a decision. They will ensure that at least a couple
|
|
|
members of the reviewing team have reviewed the document before it leaves RFC.
|
|
|
|
|
|
-If the proposal is ready, the review manager will put out a last call for
|
|
|
-community comments on the main discussion topic. If nothing significant arises,
|
|
|
-the reviewing team will be asked to start making a decision after a day.
|
|
|
+The review manager will announce a planned end to the community comment period
|
|
|
+on the "Evolution > RFCs" topic. The message will specify the end date, which
|
|
|
+will be at least one week (or four working days, if longer) after the
|
|
|
+announcement. If nothing significant arises, the reviewing team will be asked to
|
|
|
+start making a decision as scheduled. Otherwise, the review manager may extend
|
|
|
+the comment period by posting another message to the "Evolution > RFCs" topic.
|
|
|
|
|
|
##### Actions
|
|
|
|