lzap
September 17, 2021, 7:36am
1
Hello,
it looks like we missed the test week for 3.0 which is a shame - this is also a trigger for me to release all plugin versions I maintain. Tomer has always been bugging me a week before the event. Can you put this somewhere into the release process notes @upadhyeammit ? Literally:
“Poke lzap to start a test week once RC1 is ready for release”.
I will do the rest. Thanks!
Allright people, let’s test the Foreman 3.0 GA release now! Report bugs
ekohl
September 17, 2021, 8:42am
2
Could you submit a PR to the procedure? I think this is roughly the right place:
- [ ] Kick off the [release pipeline](https://ci.theforeman.org/job/foreman-<%= short_version %>-release-pipeline/) by calling [`release_pipeline`](https://github.com/theforeman/theforeman-rel-eng/blob/master/release_pipeline)
- [ ] Kick off the [client pipeline](https://ci.theforeman.org/job/foreman-client-<%= short_version %>-rpm-pipeline/) by calling [`PROJECT=client release_pipeline`](https://github.com/theforeman/theforeman-rel-eng/blob/master/release_pipeline)
- [ ] Kick off the [plugins pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-rpm-pipeline/) by calling [plugins_pipeline](https://github.com/theforeman/theforeman-rel-eng/blob/master/plugins_pipeline)
# 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 is_rc && full_version.end_with?('1') %>- [ ] 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
<% end -%>
<% if full_version.end_with?('0') %>- [ ] Update the `foreman_version` to <%= short_version %> in website's [`_config.yml`](https://github.com/theforeman/theforeman.org/blob/gh-pages/_config.yml) file
<% end -%>
- [ ] Announce the release on [Discourse](https://community.theforeman.org/c/release-announcements/8)
- [ ] Update the topic in #theforeman channel on Freenode
- [ ] Share the release announcement on twitter
<% if full_version.end_with?('0') %>- [ ] After about a week, update `stable` version in [foreman-infra](https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/profiles/manifests/web.pp#L24)
<% end -%>
- [ ] Release pipeline will trigger [foreman-plugins-<%= short_version %>-deb-test-pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-deb-test-pipeline/) and [foreman-plugins-<%= short_version %>-rpm-test-pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-rpm-test-pipeline/). These don't block releases but can be used to understand known issues around plugin compatibility with Foreman <%= short_version %>.
1 Like
