Foreman 3.18.0-rc1 is now available!
Please help by testing and getting it release-ready, and let us know if you hit any issue when upgrading or installing the release candidate either here or on our issue tracker.
This is also a good time to improve translations for existing locales to ensure full coverage. Help out at: Foreman localization. See String Freeze and State of translations - Foreman 3.18 as well.
Packages may be found in the 3.18 directories on both deb.theforeman.org and yum.theforeman.org, and tarballs are on downloads.theforeman.org.
The GPG key used for signing RPMs and tarballs has the following fingerprint:
CAB7B75A67A3DE88F9F76C3728D5752EFF70B304
The GPG key used for signing DEBs has the following fingerprint:
5B7C3E5A735BCB4D615829DC0BDDA991FD7AAC8A.
2 Likes
Thanks @ogajduse
Found something in the Release Notes. For ‘Support for Agama installer (SLES16) (#38877)’ the first PR in the projects.theforeman.org isn’t about Agama support. Maybe wrong reference. And, unfortunately, the PR for SLES16 support is not yet merged - maybe we should do this before final release of 3.18
1 Like
I somehow missed your comment, Bernhard. Apologies. It’s definitely something we should take a look at.
Let me ask @ekohl before I do something silly. Ewoud, how do we, or how would you approach this?
It appears that Titani created an incorrect reference in her PR, and it caused the closure of Feature #38877: Support for Agama installer (SLES16) - Foreman. I can’t think of any other way than rewriting the git history. Which, of course, is not an option. So I think we’re left with modifying Redmine.
But what to do with the PR is unclear to me. Should we reference it in release notes? If yes, with Redmine reference or without? If with, should I create it?
1 Like
