Create a release checklist

[mart-sessman]

Needs a proper pre- and post-release checklist with assignments

[mart-sessman]

TEDI release checklist

Keep in mind

• Always merge libraries to main branch through pull requests
• Always use merge commit. Do not use squash
• Each library has single responsible person for given release

React

• merge rc -> main
• review release notes, update migration guide(s)
• update Zeroheight release notes, add references to migration guides
• update Zeroheight component status table
• update Zeroheight deprecated components table

Angular

• merge rc -> main
• review release notes, update migration guide(s)
• update Zeroheight release notes, add references to migration guides
• update Zeroheight component status table
• update Zeroheight deprecated components table

Core

• review release notes, update migration guide(s)

Figma

• Update Zeroheight component status table
• Update Figma component statuses according to dev componentes (React, Angular) - component and variant level
• Add Component links to Figma (React, Angular)
• Publish Figma after post-release actions again (removing/adding variant level states changes component)

Community

• Announcement to Slack general channel

[karolin-kivisikk]

Figma alla läheks:

• Update Zeroheight component status table
• Update Figma component statuses according to dev componentes (React, Angular) - component and variant level
• Add Component links to Figma (React, Angular)
• Publish Figma after post-release actions again (removing/adding variant level states changes component)