Pajamas Component Migration - Phase 2
In Q3 and Q4 FY21, we used shared OKRs to make progress against implementing SSOT components in the GitLab product. While we're pleased with the progress we've made, we believe it's time to shift to a different approach that is more efficient for larger migrations and makes space for more difficult component migrations to be a part of our regular workstreams.
As a next step, we'd like to try a parallel process where we migrate some components in a mass migration, while also continuing work on individual component migrations. As a pilot, we propose starting with mass migrating buttons, because they are prolific and low(er) risk.
Mass migrating HAML buttons (pilot)
Starting March 22, we propose:
Identify UX + FE engineers per Group and align with them to have time Mar 23-24
@samdbeckham Monday (Mar 22): Have an MR ready with all button changes. Get pipelines green. !56968 (merged)
Tuesday/Wednesday (Mar 23-24): Send 10 UX + 10 FE engineers the review app, and have them identify any problems. For minor problems (for example, button alignment off by a few pixels), open an issue and apply the UI polish label. For major problems, add a comment to this issue and @mention Tim Zallman.
Thursday (Mar 25): Meet and sign off a “Go”
Monday (Mar 29): Merge the MR, so its on production by Tuesday
Tuesday (Mar 30): Have all Frontend aware of the activity and on standby to fix problems that only bubbled up in prod
Wednesday (Mar 31): Stage group Frontend Engineers fix minor button issues identified during week 1.
Continue to migrate individual components
- @timzallmann to choose the order of components to migrate, so we can burn down a component at a time.
- Frontend Engineers will continue to pick up individual instance migrations when they have extra time -- for example, while they’re waiting for a pipeline to run, etc.