Skip to content

Commit 9e0fb79

Browse files
authored
docs: release on first day of the sprint (#1387)
#### What this PR does / why we need it As discussed in Slack, we want to make release schedule more strict. New releases should be produced on the first day of new sprint.
1 parent f60fa78 commit 9e0fb79

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

RELEASE_PROCESS.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,8 @@ and delivered to end users willing to test the new release.
3030

3131
### Schedule
3232

33-
Minor releases are done every sprint, i.e. every two weeks. To be even more precise,
34-
technically speaking, two releases are produced every sprint:
33+
Minor releases should be produced on the first day of every sprint, i.e. every two weeks. To be even more precise,
34+
technically speaking, two releases are done every sprint:
3535

3636
* Release Candidate for the current version in main
3737
* Promotion of the previous sprint's candidate to an official minor version, which means there

0 commit comments

Comments
 (0)