Page MenuHomePhabricator

Document product/release cycle
Open, NormalPublic


Document release stages/methodology on

  • mobile web / desktop / app
  • alpha->beta->production
  • criteria for moving from one stage to the next
  • criteria for using beta features vs. ride the train vs. SWAT

Link from

Base off information in -

Focus on product methodology, not deployment mechanics - link out to Greg's pages for those

Draft at

Event Timeline

Eloquence raised the priority of this task from to Needs Triage.
Eloquence updated the task description. (Show Details)
Eloquence changed Security from none to None.
Eloquence added a subscriber: Eloquence.
Byfserag triaged this task as Normal priority.Oct 17 2014, 11:19 AM
Byfserag added a subscriber: Byfserag.

October version of this will focus purely on the alpha->beta->production release practices on app, mobile web & desktop web. Development/deployment methodology outside those methods will be described in a future iteration.

@howief has a draft that he is circulating within the product team.

Qgil added a subscriber: Qgil.Oct 23 2014, 3:03 PM

It would be good to have good connection between this document and the guidelines produced at T558: Goal: Common project management guidelines to be followed by teams and individual contributors are published.

Qgil added a subscriber: Wwes.

This old task is still valid, and it is in fact a priority currently. Now there is

@Wwes, who should be this task assigned to?

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptNov 18 2015, 10:48 AM

Same as T665, this is not on the TPG radar because our process work will not include owning specifics and details; teams who actually do the work will be responsible for the level of detail in this ticket and TPG will facilitate.

Given the age and inactivity of this task, I am removing the 'Team-Practices' tag in an effort to tidy up TPG backlogs/boards.

If this begins moving forward at some point in the future and you'd like to loop us in again, feel free to re-add the 'Team-Practices' tag.