This task came out of our team offsite in May.
My understanding of the proposal:
- Automate the weekly branch cut (Jenkins job or similar)
- Cut the new branch on Thursday each week (NB: reminder on the security patches issue...)
- Deploy that branch to a new Beta Cluster wiki (weekly.*, naming....) utilizing multiversion
- NB: For the avoidance of doubt: The already in place wikis in the Beta Cluster will still update every 10 minutes.
- Run all (? core? some subset automatically findable in the source trees?) e2e/browser tests against that wiki
- Encourage people to do their QA on that Beta Cluster wiki starting on Thursday and over the weekend
- Pending a healthy situation (no blocking bugs found and reported), deploy that new branch following the same process that we have now
If this is still accurate on how we want to do this (broadly speaking; I think there was discussion of moving around the days a bit), then I see three sub-tasks: 1) automating the cut, 2) setting up multiversion and the weekly deploy to Beta Cluster, and 3) identifying the e2e tests to run against that wiki