Foreman 3.0.0 RC1 is ready for testing

Foreman 3.0.0-RC1 is now available for testing. Special thanks to everyone who contributed and taken part in making this release ready.

Keep in mind that this is a major release and includes the extraction of much of the Puppet integration to a new plugin that is installed by default. Puppet users are advised to read Puppet in 3.0 release for an overview of what to expect in this and future releases.
Users who do not use puppet in their environment are encouraged to attempt disabling the plugin if possible while testing the release candidates and report and issues that may arise.

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 .

There are likely still some updates needed in the installation instructions and other parts of the documentation. We are in the process of migrating the documentation to the new Documentation website, any assistance in this effort is much appreciated! See Docs.theforeman.org webpage help needed for more information. If all goes well, Foreman 3.0 will be the last release that uses the old manual format.

Installation quick start:
https://theforeman.org/manuals/3.0/quickstart_guide.html

Upgrade instructions:
https://theforeman.org/manuals/3.0/index.html#3.6Upgrade

Release notes:
https://theforeman.org/manuals/3.0/index.html#Releasenotesfor3.0

This is also a good time to improve translations for existing locales to ensure full coverage. Help out at: Foreman localization

Packages may be found in the 3.0 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:
C8B9E30B0DBCAB595E98DF5C965467189B776908.
The GPG key used for signing DEBs has been rotated and has the following fingerprint:
5B7C3E5A735BCB4D615829DC0BDDA991FD7AAC8A.

3 Likes

I’m trying to prepare a new release notes guide for the upstream.
At the moment, the notes aren’t easy to link to, they are buried under the guide names.
I had lots of helpful suggestions from @ekohl about adding in corresponding Katello release notes.
In my proposal, the Foreman and Katello release notes would build from a single source and display in a particular order depending on whether it is a Foreman or Katello build.

One item that is problematic is that linking is handled differently in asciidoc compared to markdown.
Would this be something that is easy-ish to fix in the release notes script?