Open Bug 1574577 Opened 5 years ago Updated 4 months ago

[meta] Delivery channels content and intake

Categories

(Shield :: General, task)

Product:
Shield
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: shell, Unassigned)

References

(Depends on 8 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:

  1. 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
  2. Which channel to use when - decision matrix
  3. Clear launch path and pre-release checklists
Depends on: 1574584
See Also: → 1323547
Depends on: 1582794
Depends on: 1440782, 1474394, 1474396
No longer depends on: 1440782
Depends on: 1575948
Depends on: 1591279
Depends on: 1591285
Depends on: 1563049
No longer depends on: 1591285
Depends on: 1474397
Depends on: 1586724
Depends on: 1586760
Depends on: 1594562
Depends on: 1594607
Depends on: 1619665
Depends on: 1613647
Depends on: 1628112
You need to log in before you can comment on or make changes to this bug.