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.
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
Declare explicit roles in procedures #378
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,15 @@ | ||
[ ] Make this post a wiki | ||
|
||
## Roles | ||
|
||
* Release Owner: <%= owner %> | ||
* Release Engineer: <%= engineer %> | ||
* Installer Maintainer: @ | ||
|
||
# Manual updates: <%= target_date %> | ||
|
||
## Release Engineer | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should these headers repeat the username? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interesting idea. |
||
|
||
- [ ] Update manual if applicable for any additional installation steps | ||
- Update [release notes section](gh-pages/_includes/manuals/<%= short_version %>/1.2_release_notes.md) in the manual: | ||
- [ ] Release notes: bullet point list by category of all changes, include link to bug numbers. You can auto-generate changes using the [release notes script](https://github.com/theforeman/theforeman.org/blob/gh-pages/scripts/release_notes.rb). | ||
|
@@ -17,8 +25,13 @@ | |
|
||
# Preparing code: <%= target_date %> | ||
|
||
## Installer Maintainer | ||
|
||
- [ ] Make patch releases of installer modules that have important changes | ||
- [ ] Branch to MAJ.MIN-stable if recent changes to the module aren't suitable for patch (x.y.z) release | ||
|
||
## Release Owner | ||
|
||
<% unless (is_rc || full_version.end_with?('0')) %>- [ ] Add a new [Redmine version](https://projects.theforeman.org/projects/foreman/settings/versions) for the next minor, unless the series is EOL. Be sure the version is set to sharing with subprojects. | ||
<% end %>- [ ] Remove/change target version field for any open Redmine tickets assigned to the release still (next minor, unset it or reject) | ||
- [ ] Ensure that code in git matches issues fixed in <%= full_version %> in redmine. [issues.rb](https://gist.github.com/tbrisker/3320097f1d8c9abfb2dbcf8d8e216bba) can be used to generate a comparison between the two. | ||
|
@@ -27,6 +40,8 @@ | |
|
||
# Tagging a release: <%= target_date %> | ||
|
||
## Release Owner | ||
|
||
- In foreman <%= short_version %>-stable: | ||
- [ ] Make sure [test_<%= short_version.tr('.', '_') %>_stable](https://ci.theforeman.org/job/test_<%= short_version.tr('.', '_') %>_stable/) is green | ||
<% if (is_rc || full_version.end_with?('0')) %> - [ ] run `make -C locale tx-update` | ||
|
@@ -39,6 +54,9 @@ | |
- In foreman-installer <%= short_version %>-stable: | ||
- [ ] Tag the release using [tag.sh](https://gist.github.com/tbrisker/d51cedea51ccbcca00e72c1fc61550fe) `tag.sh <%= full_version %> && git push upstream <%= short_version %>-stable --follow-tags` | ||
- [ ] Run the Jenkins [Tarballs Release](https://ci.theforeman.org/job/tarballs-release/) to create tarballs | ||
|
||
## Release Engineer | ||
|
||
- [ ] Update release version similar to [here](https://github.com/theforeman/theforeman-rel-eng/commit/2029a9688da00d9c385c3438dd71b594ba5f728e) | ||
- [ ] Sign Tarballs | ||
- [ ] [Download](https://github.com/theforeman/theforeman-rel-eng/blob/master/download_tarballs) | ||
|
@@ -49,6 +67,8 @@ Note: If for some reason there was an issue with the tarballs that required uplo | |
|
||
# Packaging a release: <%= target_date %> | ||
|
||
## Release Engineer | ||
|
||
[Background documentation](https://projects.theforeman.org/projects/foreman/wiki/Release_Process#Packaging-a-release) | ||
|
||
- [ ] Update [foreman-packaging](https://github.com/theforeman/foreman-packaging) | ||
|
@@ -77,6 +97,8 @@ Note: If for some reason there was an issue with the tarballs that required uplo | |
|
||
# After the packages have been released | ||
|
||
# Release Owner | ||
|
||
<% unless is_rc %>- [ ] Update the versions on the website in [version](https://github.com/theforeman/theforeman.org/blob/gh-pages/_includes/version.html) and [latest news](https://github.com/theforeman/theforeman.org/blob/gh-pages/_includes/latest_news.html) | ||
<% end -%> | ||
<% if full_version.end_with?('0') %>- [ ] Update the `foreman_version` to <%= short_version %> and add the <%= short_version %> in `foreman_versions` list in website's [`_config.yml`](https://github.com/theforeman/theforeman.org/blob/gh-pages/_config.yml) file | ||
|
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentionally left empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it was sort of a one-off and I wasn't entirely sure if we should add it to the branch command.