This issue considers the launch plan for Threads.

• We intend to launch Threads with m.threads implemented
• We will launch on different platforms at different times
  • All clients should be Threads aware before the first launch (web)
• 3 rounds of testing will take place on each platform before launch: Smoke testing, User testing, & Acceptance testing

Until we're using m.threads we will not launch or default Threads to 'on' in any environment. More info in comments

Rollout plan for Threads

Beta is opt-in for the first release to stable environments.
Why? We are confident in our solution but given the known limitations of our implementation at this time we want to continue to allow users to chose to use Threads. The biggest piece of this is the outstanding work on Notifications.

Step 1: Opt-in Beta

• On Mobile, Threads remains available in Labs as they are today
• On Web, we want to promote Threads out of Labs but disabled by default

Step 2: Opt-out Beta

• Once we have read receipts, notifications, sort ordering of the thread list, and confidence in the stability and reliability of threads we will move the Beta to opt-out (Fast follow issue complete)

Step 3: Out of Beta

• Polish and stability of Threads improved we’ll remove the Beta/Labs flags and promote Threads