1.14 branched

Development
1

1.14-stable has been branched in all main repositories for the Foreman
1.14.0 release. Sorry for being a week behind schedule
(Foreman 114 Schedule - Foreman).

I aim to release 1.14.0-RC1 in a week or so once the installer modules
are ready, some initial release notes are written and it all looks
reasonably stable. RCs of .0 will follow about every two weeks until
it's stable enough to release.

  1. community-templates is branched - maintainers please cherry-pick
    fixes to 1.14-stable as you wish and I'll run the sync script on each
    release of Foreman.

  2. theforeman.org 1.14 manual is present - there's a task list at
    https://github.com/theforeman/theforeman.org/issues/708 and I'd love
    help with this.

  3. Packages and repositories have all been branched. This means that
    1.11 plugin repositories are no longer maintained (keeping nightly +
    three stable branches).

  4. Installer modules all need changelogs and to be released.

  5. Foreman's POT is now up to date, Transifex should be updated
    automatically in a day's time.

  6. A new Hammer CLI release would be appreciated for inclusion in RC1.

  7. Plugin authors should release new versions if necessary for
    compatibility with 1.14-stable (i.e. if you have fixes for develop,
    release them now.)

  8. Issues are tracked on
    Open 1.14.4 tickets - Foreman,
    please keep it refreshed as it'll change frequently when the RCs are
    available.

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

> 1.14-stable has been branched in all main repositories for the Foreman
> 1.14.0 release. Sorry for being a week behind schedule
> (Foreman 114 Schedule - Foreman).
>
> I aim to release 1.14.0-RC1 in a week or so once the installer modules
> are ready, some initial release notes are written and it all looks
> reasonably stable. RCs of .0 will follow about every two weeks until
> it's stable enough to release.
>
> 1. community-templates is branched - maintainers please cherry-pick
> fixes to 1.14-stable as you wish and I'll run the sync script on each
> release of Foreman.
>
> 2. theforeman.org 1.14 manual is present - there's a task list at
> https://github.com/theforeman/theforeman.org/issues/708 and I'd love
> help with this.
>
> 3. Packages and repositories have all been branched. This means that
> 1.11 plugin repositories are no longer maintained (keeping nightly +
> three stable branches).
>
> 4. Installer modules all need changelogs and to be released.
>
> 5. Foreman's POT is now up to date, Transifex should be updated
> automatically in a day's time.
>
> 6. A new Hammer CLI release would be appreciated for inclusion in RC1.
>
> 7. Plugin authors should release new versions if necessary for
> compatibility with 1.14-stable (i.e. if you have fixes for develop,
> release them now.)
>
> 8. Issues are tracked on
> Open 1.14.4 tickets - Foreman,
> please keep it refreshed as it'll change frequently when the RCs are
> available.

  1. I'd really want to ask for reviewers on
    https://github.com/theforeman/foreman/pull/3961 - we shouldn't ship a
    version with a CVE.

I've split some of the work to make the behavior of taxonomies more
consistent to: https://github.com/theforeman/foreman/pull/4070

The general gist is that once taxonomies are enabled, we should do a
good job at ensuring users don't create objects they can't use later,
and basically everything should be 'taxed'

If you need help understanding taxonomix.rb, I'd be glad to answer
questions.

··· On 12/06, Dominic Cleal wrote:

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

–
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato