Release Partners 12/9/2021

[joshblack]

This week, we're talking about our beta 3 release and our plans for January 2022.

Agenda

• Beta 3 Release
• Release Candidate 0
• Audit
• Research
• Q&A

Beta 3 Release

This is our last beta release for v11. It includes a number of bug fixes for layers, themes, and bundles along with new components and better support for IBM Plex.

The draft post for this release is available here.

Release Candidate 0

Our next scheduled release is January 27th and will be our Release Candidate 0 release. This release will include all feature additions that will make it into v11. After this release, no new features or functionality will be included.

For this release, the focus will shift from primary development to bug fixes, QA, and migration.

Links & Resources

• v11 Release Candidate 0 #10245

Audit

Starting in 2022, we will begin an internal audit of our work leading up to v11. This audit will include a variety of checks, including (but not limited to):

• Consistent appearance across browsers
  • Components use the correct tokens
• Consistent behavior across browsers
• Documentation has been updated on our website and storybook
• Migration documentation is available, if applicable

Research

As we move towards a stable release of v11, we are aiming to work with PALs and product teams to minimize the time it takes to migrate. The hope is to work with these teams in waves, starting with wave 1 in January and moving towards wave 2 and 3 in February and March.

Each wave will include a partnership between Carbon and teams in the wave to attempt a migration to v11 and provide feedback on the migration path and quality of the release itself. This could be done through experimental releases, prototypes, or other avenues.

We'd love to hear what you all think about this proposal and if it would work with your workstreams in 2022 and what you would be interested in helping with.

[joshblack]

Q&A

• IBM Products would love to move forward but know that certain product teams won't want to
  • How do we handle balancing enhancements and migration?
  • Even with Carbon 10, not all teams have migrated to it yet
  • Anything built on top of Carbon has this question:
    • Do you have two strands for v10 and v11, or do you switch from 10 to 11? If so, when?
• It'd be incredibly helpful to have tooling, lining for how to move from 10 to 11

Questions

• Does there need to be a mandate for v11?
  • It helps when someone says "all products need to move over to v11", their work shifts to support on v10 and can dedicate to migrating
• What does it mean if a page uses "Carbon v10"?

Next steps

• Reach out to Lee and ask about v10 compliance
• Reach out IBM Products about how to manage parallel paths