potential changes:
- react 17 BREAKING (Priority = 1)
- What's the work?
- Spike - - STCOM-864Getting issue details... STATUS
- Create stripes component ticket and assign to John
- Create stripes smart component ticket and assign to [TBD] - KG will speak with Denys
- Create stripes-core ticket and assign to [TBD] - Zak will speak with Holly
- Create stripes-connect ticket and assign to RyanB
- Create stripes-form and final form and assign to Zak
- Who needs to be involved?
- Every repo
- Deadline to make sure we do not muck up Kiwi development?
- August 10th (maybe earlier)
- Do we need someone to help coordinate dependencies/work?
- Create a rancher environment with react 17 branch [KG will talk with dev ops]
- Do not merge changes to master until PO/Dev validation on rancher environment
- What's the work?
- Define relationship and expectations with security team (Priority = 2)
- Next step: Discussion topic with stripes-arch led by John THEN discuss with security team
- Determine security vulnerability threshold - development [stripes-force | deliverable - documentation]
- Determine security vulnerability threshold - production [stripes-force | deliverable - documentation]
- Next step: Discussion topic with stripes-arch led by John THEN discuss with security team
- Storybook upgrade - security vulnerability (
-
STCOM-863Getting issue details...
STATUS
) (Priority = 5)
- Identify a new storybook owner
- Get agreement from Filip/Rasmus - KG NEEDS TO DO IT
- local resource with redux, recoil, whatever
- rxjs 6 BREAKING (Priority = 3)
- Per Zak - this is complete. We need to do at the same time as react17.
- node-15/node-16/npm-7 (Hold for Lotus R12022)
- encourage people to go this route with
--legacy-peer-deps
- put ourselves in a position to drop
--legacy-peer-deps
by 2022-R1?
- encourage people to go this route with
- webpack v5?
- focus management
- migrate stripes-components off BigTest OG (Priority = 4)