Add Foreman 3.18 Release Notes

[ogajduse]

What changes are you introducing?

Foreman 3.18 release notes. This mostly a reformat of theforeman/theforeman.org#2275.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Contributor checklists

• I am okay with my commits getting squashed when you merge this PR.
• I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• Foreman 3.18/Katello 4.20 (Satellite 6.19)
• Foreman 3.17/Katello 4.19
• Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6)
• Foreman 3.15/Katello 4.17
• Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
• Foreman 3.13/Katello 4.15 (EL9 only)
• Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
• We do not accept PRs for Foreman older than 3.12.

[github-actions]

The PR preview for b64c71e is available at theforeman-foreman-documentation-preview-pr-4649.surge.sh

The following output files are affected by this PR:

• Release_Notes/index-foreman-deb.html
• Release_Notes/index-foreman-el.html
• Release_Notes/index-foremanctl-katello.html
• Release_Notes/index-foremanctl-orcharhino.html
• Release_Notes/index-foremanctl-satellite.html
• Release_Notes/index-katello.html
• Release_Notes/index-orcharhino.html
• Release_Notes/index-satellite.html

show diff

show diff as HTML

[aneta-petrova]

I didn't review the lines that are copied from redmine (IMO that's preferable to keep them in sync with the issue headings in redmine).

[aneta-petrova]

To highlight that it's users who must take action:

Suggested change

	Systems still using GRUB1 for provisioning must migrate to GRUB2 before upgrading.
	If your system is using GRUB1 for provisioning, migrate to GRUB2 before upgrading.

[aneta-petrova]

Is there a link we can leave here for users, to take them somewhere where they'll find instructions on migrating to GRUB2?

[ogajduse]

That's a spot-on question!
@arvind4501 @stejskalleos, mind chiming in here?

[ogajduse]

I didn't review the lines that are copied from redmine (IMO that's preferable to keep them in sync with the issue headings in redmine).

Based on the review comments I received in theforeman/theforeman.org#2275, I edited the Redmine issue titles. While it is preferable to keep them in sync, we can adjust the issue title(s) in Redmine for them to "look good" in release notes.

[maximiliankolb]

I left some comments on the change log entries. Feel free to adjust or ignore them as you see fit.

[ogajduse]

@Lennonka, I came across #4613, but I recommend implementing it in a separate PR. My goal with this PR is to have the release notes merged ASAP so we can announce the release.

[Lennonka]

I came across #4613, but I recommend implementing it in a separate PR. My goal with this PR is to have the release notes merged ASAP so we can announce the release.

@ogajduse Fine with me. I'll add it afterwards. Thanks for checking!

[ogajduse]

Given that we were supposed to release on February 10th, I'm going to merge this PR. Thank you @aneta-petrova and @maximiliankolb for your feedback! If you'd like to change the wording of these release notes, please raise it with me in chat or tag me in a PR here in this project. I'm open to any feedback or changes.

[maximiliankolb]

Thank you Ondřej