I propose the following policy apply to the 2.2.x branch, once (and if)
it is created:

Before GA: A 'soft' CTR.  Any small bug fixes can be directly committed.
  Any API changes must be reviewed by the list. (lazy consensus).  Any
large changes must get voted on.

After first GA: Standard RTC, as done on 2.0.x.

Reply via email to