Have cooldown weeks or days for breaking changes in CI #3927
Replies: 4 comments
-
Proposal: for our two-week sprints, the second week/week leading up to a release/tag, we pause merging changes to CI until the tag is done. Fixes to CI would still be allowed to merge |
Beta Was this translation helpful? Give feedback.
-
Proposal: freeze the CI changes in the second way of the sprint and create the release in that week. |
Beta Was this translation helpful? Give feedback.
-
Extra Proposal: When the PR backlog is large or urgent, we pause breaking CI changes until those PRs merge. Here are some rough guidelines for "large or urgent":
|
Beta Was this translation helpful? Give feedback.
-
I feel like we already do this now |
Beta Was this translation helpful? Give feedback.
-
Sometimes making a bunch of changes to CI might have a great impact on development if something fails. We might want to reduce this changes in specific dates.
Beta Was this translation helpful? Give feedback.
All reactions