CONTRIBUTING: Update the release schedule: Increase cadence by a week #709
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eskultety
requested review from
a-ovchinnikov,
brunoapimentel,
taylormadore,
ben-alkov and
slimreaper35
a-ovchinnikov
approved these changes
Oct 25, 2024
slimreaper35
approved these changes
Oct 25, 2024
eskultety
force-pushed
the
contributing-release-update
branch
from
af1738b
to
3bfb655
Compare
a-ovchinnikov
approved these changes
Oct 25, 2024
|
/retest |
2 weeks may be too slow for some ultra-agile, rapid development consumers of this project, often having led to breaking the scheduled pattern and resorting to releases on an ad-hoc basis. Let's shorten the schedule by a week, describing scenarios at which a given release may be at risk. Signed-off-by: Erik Skultety <[email protected]>
eskultety
force-pushed
the
contributing-release-update
branch
from
3bfb655
to
12c4206
Compare
Merged
via the queue into
containerbuildsystem:main
with commit Oct 29, 2024
12543fc
14 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2 weeks may be too slow for some ultra-agile, rapid development consumers of this project, often having led to breaking the scheduled pattern and resorting to releases on an ad-hoc basis. Let's shorten the schedule by a week, describing scenarios at which a given release may be at risk.
Maintainers will complete the following section
Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:
/ok-to-test(as is the standard for Pipelines as Code)