Open
Bug 1574577
Opened 5 years ago
Updated 5 years ago
[meta] Delivery channels content and intake
Categories
(Shield :: General, task)
Shield
General
Tracking
(Not tracked)
NEW
People
(Reporter: shell, Unassigned)
References
(Depends on 9 open bugs)
Details
Delivering any content outside of “riding the train” needs clear boundaries and guidelines. The critical issue is “hot fix” channel, but there are other content delivered requests outside of traditional “train release” that should be clarified at the same time.
Clearly define:
- The type of content allowed - so we can document the boundaries for teams and give clear guidance on requirements for content in each delivery channel
- Which channel to use when - decision matrix
- Clear launch path and pre-release checklists
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•