1.13 being branched

Development
1

This week I've started the branch process for 1.13, which ought to be
mostly complete within a day or so.

I hope to be able to release 1.13.0-RC1 in a week once all of the
sub-projects are released (i.e. installer modules), some initial docs
are written and tests + packages seem reasonably complete and stable.

In detail:

  1. community-templates was synced into Foreman yesterday and has been
    branched to 1.13-stable, maintainers should cherry-pick fixes as desired
    to the stable branch.

  2. theforeman.org manual has been copied from 1.12 to 1.13, list of
    tasks is at https://github.com/theforeman/theforeman.org/issues/649 and
    PRs can be made against gh-pages:_includes/manuals/1.13/.

  3. Koji tags are copied from nightly to 1.13 tags, rpm/develop branched
    to rpm/1.13. I'll copy the Debian repos shortly and branch that too.

  4. Some installer Puppet modules need to be released - dns, dhcp, git,
    tftp are all up to date, but foreman, foreman_proxy and puppet need
    releasing.

  5. Core projects will be branched shortly, probably at their current
    revisions.

  6. Foreman's source POT is relatively up to date on Transifex and I'll
    switch it over to the 1.13-stable branch when available. Translations
    made now will be going into 1.13.x.

  7. Hammer CLI 0.8.0 is available, but packages need updating. A PR is
    open for Debian, but RPMs need doing, preferably in time for RC1.

··· -- Dominic Cleal dominic@cleal.org
2

> From: "Dominic Cleal" <dominic@cleal.org>
> To: "foreman-dev" <foreman-dev@googlegroups.com>
> Sent: Tuesday, September 6, 2016 9:29:23 AM
> Subject: [foreman-dev] 1.13 being branched
>
> This week I've started the branch process for 1.13, which ought to be
> mostly complete within a day or so.
>
> I hope to be able to release 1.13.0-RC1 in a week once all of the
> sub-projects are released (i.e. installer modules), some initial docs
> are written and tests + packages seem reasonably complete and stable.
>
> In detail:
>
> 1. community-templates was synced into Foreman yesterday and has been
> branched to 1.13-stable, maintainers should cherry-pick fixes as desired
> to the stable branch.
>
> 2. theforeman.org manual has been copied from 1.12 to 1.13, list of
> tasks is at https://github.com/theforeman/theforeman.org/issues/649 and
> PRs can be made against gh-pages:_includes/manuals/1.13/.
>
> 3. Koji tags are copied from nightly to 1.13 tags, rpm/develop branched
> to rpm/1.13. I'll copy the Debian repos shortly and branch that too.
>
> 4. Some installer Puppet modules need to be released - dns, dhcp, git,
> tftp are all up to date, but foreman, foreman_proxy and puppet need
> releasing.

Hi,

Can we ensure this gets in before foreman_proxy is released?
https://github.com/theforeman/puppet-foreman_proxy/pull/277

The requisite smart_proxy_pulp package is already in the repos. Just waiting
for slow travis to test it again…

It's needed for the Katello release to support publishing to Puppet 4 directories.

  • Stephen
··· ----- Original Message -----

  1. Core projects will be branched shortly, probably at their current
    revisions.

  2. Foreman’s source POT is relatively up to date on Transifex and I’ll
    switch it over to the 1.13-stable branch when available. Translations
    made now will be going into 1.13.x.

  3. Hammer CLI 0.8.0 is available, but packages need updating. A PR is
    open for Debian, but RPMs need doing, preferably in time for RC1.

–
Dominic Cleal
dominic@cleal.org

–
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.

3

> 3. Koji tags are copied from nightly to 1.13 tags, rpm/develop branched
> to rpm/1.13. I'll copy the Debian repos shortly and branch that too.

Debian repos are complete as well now.

As usual in the branching to RC1 period, we don't have any builds of
Foreman itself in the 1.13 repos, so plugin releases due for 1.13 will
need building once RC1's ready. I created
https://github.com/theforeman/foreman-packaging/milestone/2 to help keep
note of these.

> 5. Core projects will be branched shortly, probably at their current
> revisions.

All four branched to 1.13-stable now.

I've also updated the schedules for 1.13 and 1.14 (three months from
now), and will list any issues that will block the 1.13.0 RCs:
Foreman 113 Schedule - Foreman
Foreman 114 Schedule - Foreman

There are also open tickets in Redmine with the 1.13.0 release set where
they appear to be regressions against 1.12, so please keep an eye on
these and help out where possible:
http://projects.theforeman.org/projects/foreman/issues?query_id=103

··· On 06/09/16 14:29, Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org

4

These are finalised now, thanks to Michael and Ewoud for the final work.
I'll tag and release in the next day or so if nightly tests pass again.

RC1 will probably be released around Tuesday 13th Sept.

··· On 06/09/16 14:29, Dominic Cleal wrote: > 4. Some installer Puppet modules need to be released - dns, dhcp, git, > tftp are all up to date, but foreman, foreman_proxy and puppet need > releasing.

–
Dominic Cleal
dominic@cleal.org