doc:Ask reviews to reject new legacy notifications
The versioned notificaton infrastructure is in place and the team agreed on the midcycle to allow new notification types only based on the versioned notification infrastructure. So the code-review document is updated to reflect this decision Change-Id: I7f3860ca59658dc21e67f26bb45341cb46da2235 Partially-Implements: bp versioned-notification-api
This commit is contained in:
parent
05adc8d006
commit
028ff49b2a
@ -268,3 +268,9 @@ Three sections are left intentionally unexplained (``prelude``, ``issues`` and
|
||||
``other``). Those are targeted to be filled in close to the release time for
|
||||
providing details about the soon-ish release. Don't use them unless you know
|
||||
exactly what you are doing.
|
||||
|
||||
|
||||
Notifications
|
||||
=============
|
||||
* Every new notification type shall use the new versioned notification
|
||||
infrastructure documented in :doc:`notifications`
|
||||
|
Loading…
Reference in New Issue
Block a user