1.8 branching in about a fortnight

I'll be branching core Foreman repos in about a fortnight for the
Foreman 1.8 series.

The schedule is at
http://projects.theforeman.org/projects/foreman/wiki/Foreman_18_Schedule

There are a few technical release blockers, so any help to resolve these
before branching is appreciated.

  1. Bug #8874: gettext 3.1.13+ causes locale tx-update errors due to .edit.po files - Foreman - gettext 3.x support,
    need to figure out how plugins can work (I could use some help)

  2. Feature #4478: API docs need to be localized - Foreman - API i18n support, RPMs
    mostly done (I'm reviewing right now), debs still to do.

  3. Feature #8710: Break out foreman-debug into separate package - Foreman - foreman-debug
    subpackage, as core commits are in, debs still to do.

Thanks to Marek for working on and triaging the fallout of the network
changes, that seems to be going smoothly.

Anything and everything that happens up until branching and some things
after that will make it into the release as usual. Please let me know
about any regressions that may prevent releasing.

··· -- Dominic Cleal Red Hat Engineering

I forgot to include the link to all blockers, which includes general
regressions and issues, mostly relating to networking right now:
http://bit.ly/172VbxZ

··· On 09/02/15 13:19, Dominic Cleal wrote: > I'll be branching core Foreman repos in about a fortnight for the > Foreman 1.8 series. > > The schedule is at > http://projects.theforeman.org/projects/foreman/wiki/Foreman_18_Schedule > > There are a few technical release blockers, so any help to resolve these > before branching is appreciated.


Dominic Cleal
Red Hat Engineering

Note to Katello users, the 1.8 Foreman release will mark the first attempt
at releasing Katello in lockstep. This means that for 2.2 we will branch at
the same time as Foreman and release within 2-3 days of Foreman 1.8 being
released in an attempt to keep those fresh Foreman features available.

Eric

··· On Mon, Feb 9, 2015 at 8:46 AM, Dominic Cleal wrote:

On 09/02/15 13:19, Dominic Cleal wrote:

I’ll be branching core Foreman repos in about a fortnight for the
Foreman 1.8 series.

The schedule is at
Foreman 18 Schedule - Foreman

There are a few technical release blockers, so any help to resolve these
before branching is appreciated.

I forgot to include the link to all blockers, which includes general
regressions and issues, mostly relating to networking right now:
http://bit.ly/172VbxZ


Dominic Cleal
Red Hat Engineering


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Three of the networking issues are still assigned without PRs, and one
general web UI issue needs fixing too (#8736). Tomas, are these on
track or is somebody able to help with one or more of those?

I think we can live without working compute profiles for RC1, but I'd
like to see them fixed by RC2.

I'll also start to mark important PRs with a "1.8 priority" label, so
please keep an eye out for that :slight_smile:

Branching should be this Monday or Tuesday, depending on the state of
develop at that point, and RC1 hopefully within a week or two if
everything comes together.

Thanks everyone!

··· On 09/02/15 13:46, Dominic Cleal wrote: > On 09/02/15 13:19, Dominic Cleal wrote: >> I'll be branching core Foreman repos in about a fortnight for the >> Foreman 1.8 series. >> >> The schedule is at >> http://projects.theforeman.org/projects/foreman/wiki/Foreman_18_Schedule >> >> There are a few technical release blockers, so any help to resolve these >> before branching is appreciated. > > I forgot to include the link to all blockers, which includes general > regressions and issues, mostly relating to networking right now: > http://bit.ly/172VbxZ


Dominic Cleal
Red Hat Engineering

> Three of the networking issues are still assigned without PRs, and one
> general web UI issue needs fixing too (#8736). Tomas, are these on
> track or is somebody able to help with one or more of those?

While I've not seen a PR yet, Tomas showed the current state to Marek
and I this week, and it's looking good. I'm hopefuly we can get it in
soon, but I'll obviously let Tomas give a definitive answer :wink:

> I think we can live without working compute profiles for RC1, but I'd
> like to see them fixed by RC2.

Agreed, but it's definitely not the ideal scenario.

Greg

··· On 19 February 2015 at 09:35, Dominic Cleal wrote:

I forgot to reply to this, sorry.

This is exactly the right thing to do IMO. I realise it's a tight
turnaround from your last release, but I think following and sorting out
the cadence now is sane. Thanks!

··· On 11/02/15 13:33, Eric D Helms wrote: > Note to Katello users, the 1.8 Foreman release will mark the first > attempt at releasing Katello in lockstep. This means that for 2.2 we > will branch at the same time as Foreman and release within 2-3 days of > Foreman 1.8 being released in an attempt to keep those fresh Foreman > features available.


Dominic Cleal
Red Hat Engineering