Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add reference to preparing next major release doc; reference automated workflow from freeze docs #422

Merged
merged 3 commits into from
Jun 15, 2024
Merged

Add reference to preparing next major release doc; reference automated workflow from freeze docs #422

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d64012b
Add reference to preparing next major release doc.
felixfontein Jun 4, 2024
00c35f6
Reference automated workflow from freeze docs.
felixfontein Jun 4, 2024
af5d033
Reformulate.
felixfontein Jun 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/automated-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,3 +149,7 @@ next to the release version:

2. Set `existing-branch` to the branch you pushed to the `ansible-build-data`
repository.

Finally, remember to prepare the directory for the next major Ansible release. How
to do this is described in [Setting up for a new major
release](new-ansible-and-freezes.md#setting-up-for-a-new-major-release).
felixfontein marked this conversation as resolved.
Show resolved Hide resolved
6 changes: 6 additions & 0 deletions docs/new-ansible-and-freezes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,12 @@ TODO: Improve the release playbook to support this case without requiring extra
Beyond the regular [Ansible Release Process](release-process.md), X.Y.0
releases require special handling before running the release playbook.

!!! note
This can be done in a simpler fashion when using the [automated release
process](automated-process.md). See the regular automated workflow for
versions up to rc1, and the [Special builds](automated-process.md#special-builds)
section for further release candidates and for the final major release.

1. Determine the previous and the current releases

``` sh
Expand Down