Release process

Release Process

This document outlines the release process for our repositories, including React, Angular components as well as tedi-core.

Branching & release cadence

1. Release candidate (rc) branch

• We continuously release updates to the rc branch.
• This serves as a staging area for testing and validation before a major release.

2. Major releases

• We perform a major release once a month, typically on the last Thursday of the month.
• During this release, we publish a stable version without the rc- prefix (e.g., 1.2.0 instead of rc-1.2.0).
• If an urgent fix or critical update is required, we may adjust the schedule accordingly.

3. Design releases

• Design component updates happen irregularly when the designer decides to release a batch.
• These releases are included in the development release notes, ensuring all new design components are documented alongside regular component changes.

Component synchronization

• React and Angular components are released simultaneously.
• tedi-core has an independent release cycle and is updated separately as needed.

Release notes & changelog

• Full release notes for React, Angular, and Tedi Core components are maintained here:
  Release Notes
• GitHub also tracks the changelog of commits and releases automatically.

This process ensures a structured approach to releasing updates while allowing flexibility for urgent changes and design-driven improvements.