Our repos and packages are branched now for Foreman 1.10, which means
we're at feature-freeze, with changes since the end of June.
New features will almost certainly go to 1.11 and beyond - please don't
hold up, just continue working on develop as usual.
My aim is to release 1.10 by the start of December, which gives us just
over one and a half months. This is slightly more than usual.
The full schedule is at
Foreman 110 Schedule - Foreman.
RC1 should be only a week or so away, then we'll continue to release
RCs every two weeks or so until it's stable enough for 1.10.0. This
gives enough scheduled time for three RCs.
To get to RC1:
Installer modules need to be released, new major/minor versions as
A few headline features need to be written up for the release notes
And for us to get to 1.10.0:
As many regressions will need to be fixed before release as possible.
Please monitor http://bit.ly/1NBaW1o for tickets assigned to the
release. Some PRs are already open but need attention, look out for
purple 1.10 labels.
Translations will switch from 1.9-stable to 1.10-stable shortly.
The Foreman manual needs filling out, see
https://github.com/theforeman/theforeman.org/issues/395 for tasks and
sections you can help with.
Bug triage will begin after RC1 is released - we'll have reports
arriving in Redmine, on IRC and on the mailing lists. Please keep an
eye out, redirect new reports into Redmine and ensure they get marked
for the release if it's a regression.
Plugin authors should start testing with nightly or 1.10-stable
branches and check for deprecation warnings during usage, tests and as
noted in the release notes on the website. If you need to make changes
for 1.10 support, please make a new release available.
Testing is always welcome, particularly upgrade testing with
different and varied databases.