1.8-stable branched

Development
1

1.8-stable has been branched in the four core Foreman repos.

There are still a few largish changes I'm expecting to land in develop
and probably the stable branch, especially around networking, so please
do continue working on them and merging into develop. I'll be trying to
minimise string changes while cherry picking so we can freeze those for RC2.

Thanks to people who have helped with triaging Redmine tickets against
develop and getting the issues sorted. Any triaged and targeted for
1.8.0 will show up on this list: http://bit.ly/172VbxZ

The 1.8 manual has been created, and this ticket lists some of the tasks
outstanding. I'll probably work on the bulk of the release notes and
headline features next week. Please feel free to PR anything you see on
the list.

https://github.com/theforeman/theforeman.org/issues/307

Puppet modules we can release (the next minor/major versions) at the
start of next week too, a couple of days before we tag the installer repo.

It looks like a Hammer release is imminent too, which we can include
either during the RC process or .1, depending on when it drops.

I'm going to be off for the latter half of this week, so will be aiming
for RC1 to be next week (commencing 2nd March) or the week after,
depending on how everything goes (e.g. setup for packages, stability of
develop).

Let me know if you have any questions or concerns over issues/inclusion
of fixes.

··· -- Dominic Cleal Red Hat Engineering
2

RC1 next week would be awesome!

Off to read the redmine issues and see if there is anything i could put
into my lab and test out.

··· On Tuesday, February 24, 2015 at 6:02:49 AM UTC-6, Dominic Cleal wrote: > > 1.8-stable has been branched in the four core Foreman repos. > > There are still a few largish changes I'm expecting to land in develop > and probably the stable branch, especially around networking, so please > do continue working on them and merging into develop. I'll be trying to > minimise string changes while cherry picking so we can freeze those for > RC2. > > Thanks to people who have helped with triaging Redmine tickets against > develop and getting the issues sorted. Any triaged and targeted for > 1.8.0 will show up on this list: http://bit.ly/172VbxZ > > The 1.8 manual has been created, and this ticket lists some of the tasks > outstanding. I'll probably work on the bulk of the release notes and > headline features next week. Please feel free to PR anything you see on > the list. > > https://github.com/theforeman/theforeman.org/issues/307 > > Puppet modules we can release (the next minor/major versions) at the > start of next week too, a couple of days before we tag the installer repo. > > It looks like a Hammer release is imminent too, which we can include > either during the RC process or .1, depending on when it drops. > > I'm going to be off for the latter half of this week, so will be aiming > for RC1 to be next week (commencing 2nd March) or the week after, > depending on how everything goes (e.g. setup for packages, stability of > develop). > > Let me know if you have any questions or concerns over issues/inclusion > of fixes. > > -- > Dominic Cleal > Red Hat Engineering >
3

Hey,

> Let me know if you have any questions or concerns over issues/inclusion
> of fixes.

first of all, thanks!

This is slightly off-topic, but I wonder what big changes are planned
for the 1.9 release. Now it's the best time to start merging big-bang
changes.

Please share your ideas, pending pull request links, thoughts or
recommendations.

For myself - after we finish with some final SELinux patches for 1.8,
I'd like to enable Smart Proxy SELinux policy by default for nightly
builds. The idea behind this is to hit the bugs early.

··· -- Later, Lukas #lzap Zapletal
4

A quick end-of-week update:

> 1.8-stable has been branched in the four core Foreman repos.
>
> There are still a few largish changes I'm expecting to land in develop
> and probably the stable branch, especially around networking, so please
> do continue working on them and merging into develop. I'll be trying to
> minimise string changes while cherry picking so we can freeze those for RC2.

Thanks to Tomas and Marek for their work on the compute
profiles/networking fixes and VM creation issues, that's been merged
into 1.8-stable - it's great to know it'll be tested in RC1.

> Thanks to people who have helped with triaging Redmine tickets against
> develop and getting the issues sorted. Any triaged and targeted for
> 1.8.0 will show up on this list: http://bit.ly/172VbxZ

There are a couple more on this list, I'd especially like help on the
scoped_search issue from somebody more familiar with ActiveRecord etc.
Please also see my recent list post about this ticket.

> The 1.8 manual has been created, and this ticket lists some of the tasks
> outstanding. I'll probably work on the bulk of the release notes and
> headline features next week. Please feel free to PR anything you see on
> the list.
>
> https://github.com/theforeman/theforeman.org/issues/307
>
> Puppet modules we can release (the next minor/major versions) at the
> start of next week too, a couple of days before we tag the installer repo.

Some have now been released, but we have a few more PRs to finish off
before we can release the last four modules (dns, foreman,
foreman_proxy, puppet).

Thanks to Ewoud and Michael for their help, we've fixed and merged a
huge number of issues this week.

> I'm going to be off for the latter half of this week, so will be aiming
> for RC1 to be next week (commencing 2nd March) or the week after,
> depending on how everything goes (e.g. setup for packages, stability of
> develop).

I'm aiming for the latter half of w/c 9th March now, due to the work
remaining to release our Puppet modules.

··· On 24/02/15 12:02, Dominic Cleal wrote:

–
Dominic Cleal
Red Hat Engineering

5

I'd like to merge Bug #4841: Package Foreman in its own SCL - Packaging - Foreman for our own
SCL and do the mass rebuild of our RPMs early in the process. So far my
tests have been good, I've been able to mass-rebuild our repos
successfully, though haven't yet fully tested the upgrade.

This will make it easier to do a Rails 4 rebuild, whenever that lands.

··· On 24/02/15 13:38, Lukas Zapletal wrote: > Hey, > >> Let me know if you have any questions or concerns over issues/inclusion >> of fixes. > > first of all, thanks! > > This is slightly off-topic, but I wonder what big changes are planned > for the 1.9 release. Now it's the best time to start merging big-bang > changes. > > Please share your ideas, pending pull request links, thoughts or > recommendations.

–
Dominic Cleal
Red Hat Engineering

6

>> Puppet modules we can release (the next minor/major versions) at the
>> start of next week too, a couple of days before we tag the installer repo.
>
> Some have now been released, but we have a few more PRs to finish off
> before we can release the last four modules (dns, foreman,
> foreman_proxy, puppet).
>
> * dns has an outstanding issue causing test failures in foreman_proxy,
> validating the SOA when the zone name is changed
> (https://github.com/theforeman/puppet-foreman_proxy/pull/159)
> * foreman should have
> https://github.com/theforeman/puppet-foreman/pull/298 merged for 1.8
> * foreman_proxy has a major lint update for Puppet 4 compat:
> https://github.com/theforeman/puppet-foreman_proxy/pull/153
>
> Thanks to Ewoud and Michael for their help, we've fixed and merged a
> huge number of issues this week.

And with one last push, we successfully released these last modules
today. Many thanks!

https://groups.google.com/forum/#!topic/foreman-users/hMwExuCklZA
announces the major module releases.

>> I'm going to be off for the latter half of this week, so will be aiming
>> for RC1 to be next week (commencing 2nd March) or the week after,
>> depending on how everything goes (e.g. setup for packages, stability of
>> develop).
>
> I'm aiming for the latter half of w/c 9th March now, due to the work
> remaining to release our Puppet modules.

I'll begin tagging some time on Tuesday, so we can hopefully see RC1
either tomorrow or Wednesday.

··· On 06/03/15 12:43, Dominic Cleal wrote:

–
Dominic Cleal
Red Hat Engineering