1.9 branched

Development
1

Our main repositories and packaging systems are now branched for the
Foreman 1.9 series, so we are pretty much at feature-freeze for 1.9.

Features can continue to be committed to develop for 1.10, so please
don't hold up on those. Small and low risk ones may even make it
through to 1.9.

We've now got a month ahead of us to get 1.9 stable and released. This
has the following strands of work:

  1. Installer modules need to be released - dns & dhcp in particular need
    major version bumps I think and we need to go over any open PRs. This
    needs to happen before RC1.

  2. Foreman manual needs itemised release notes, headline features and
    general updates for 1.9. See
    https://github.com/theforeman/theforeman.org/issues/366 for tasks. The
    release notes need to happen before RC1, the rest before 1.9.0.

  3. Regressions that block 1.9's release need to be fixed, see the
    blocker list at http://bit.ly/1FyhCnI which is updated regularly. Get
    as many done as we can before each RC.

  4. Translations for new and changed 1.9 strings will begin from tomorrow
    I hope when the string file gets pulled by Transifex. See
    https://www.transifex.com/projects/p/foreman/ for details. These will
    be pulled into each RC.

  5. Bug triage for issues found in the RCs. This begins in earnest with
    RC1, so please keep an eye out on IRC, the mailing lists and Redmine
    (Found in release: 1.9.0) for new bug reports. Please ensure
    regressions are marked for Release: 1.9.0.

  6. Plugin authors should ensure their plugins are working against 1.9,
    and release new versions if necessary for compatibility so users can
    upgrade to RCs and 1.9.0.

Usually during the RC period we'll do a new release candidate every two
weeks, with the first probably on around Monday 6th July (it'll take a
week or so to get the pre-RC1 tasks above done). We'll keep doing them
until the bug reports die down.

I'll be taking as many bug fixes onto the stable branches as I can, as
long as they look reasonably stable, so don't worry if your fix isn't in
by now as there are still a few weeks ahead before 1.9.0. Don't worry
about cherry picking things yourselves, I'll do it before each RC based
on the Redmine bug list.

Please let me know if you have any questions, and thanks to everybody
for the past three months of active development - just one more to go.

Cheers,

··· -- Dominic Cleal Red Hat Engineering
2

Talking of Foreman 1.10, I've put an approximate schedule up at
Foreman 110 Schedule - Foreman.

This assumes about a month for the 1.9 RC period, and the usual three
month gap until the next major release.

Development begins now!

··· On 26/06/15 13:46, Dominic Cleal wrote: > Our main repositories and packaging systems are now branched for the > Foreman 1.9 series, so we are pretty much at feature-freeze for 1.9. > > Features can continue to be committed to develop for 1.10, so please > don't hold up on those.

–
Dominic Cleal
Red Hat Engineering

3

> Our main repositories and packaging systems are now branched for the
> Foreman 1.9 series, so we are pretty much at feature-freeze for 1.9.
>
> Features can continue to be committed to develop for 1.10, so please
> don't hold up on those. Small and low risk ones may even make it
> through to 1.9.
>
> We've now got a month ahead of us to get 1.9 stable and released. This
> has the following strands of work:

Alright, the first release candidate went out just now.

> 1. Installer modules need to be released - dns & dhcp in particular need
> major version bumps I think and we need to go over any open PRs. This
> needs to happen before RC1.

All released, though we didn't get a couple of the puppet-4 branches
merged in time. These mostly look like test-only issues, but any
further fixes we can make in patch releases of the modules.

> 2. Foreman manual needs itemised release notes, headline features and
> general updates for 1.9. See
> https://github.com/theforeman/theforeman.org/issues/366 for tasks. The
> release notes need to happen before RC1, the rest before 1.9.0.

Plenty more to do on this, only the release notes have been done.

> 3. Regressions that block 1.9's release need to be fixed, see the
> blocker list at http://bit.ly/1FyhCnI which is updated regularly. Get
> as many done as we can before each RC.

I'm really impressed with the response to this, thanks to everybody
who's monitored for these issues and written, tested or merged fixes.
RC1 went out with the fewest number of known issues for some time.
Let's ensure we keep it up as the bug reports come in.

> 4. Translations for new and changed 1.9 strings will begin from tomorrow
> I hope when the string file gets pulled by Transifex. See
> https://www.transifex.com/projects/p/foreman/ for details. These will
> be pulled into each RC.

Big thanks to the translation teams who've been updating these multiple
times a day lately. The latest translations as of this morning are in RC1.

> 5. Bug triage for issues found in the RCs. This begins in earnest with
> RC1, so please keep an eye out on IRC, the mailing lists and Redmine
> (Found in release: 1.9.0) for new bug reports. Please ensure
> regressions are marked for Release: 1.9.0.
>
> 6. Plugin authors should ensure their plugins are working against 1.9,
> and release new versions if necessary for compatibility so users can
> upgrade to RCs and 1.9.0.

I'd just ask all plugin maintainers to recheck this and see if there's
anything they need to release - especially if you needed to change
something for 1.9 compatibility for ptable/template changes.

I'm aware of foreman_setup and foreman_templates needing releases, which
I'll arrange.

> Usually during the RC period we'll do a new release candidate every two
> weeks, with the first probably on around Monday 6th July (it'll take a
> week or so to get the pre-RC1 tasks above done). We'll keep doing them
> until the bug reports die down.

6th July was spot on, so I'll aim for two weeks from today for RC2, 20th
July.

Thanks everyone!

··· On 26/06/15 13:46, Dominic Cleal wrote:

–
Dominic Cleal
Red Hat Engineering