add 4.3.12 to fast

[vfreex]

No description provided.

[wking]

/hold

Blocked on #166 and errata publication.

[vfreex]

PR updated.

[wking]

#166 is still open, so this can happen or not without much impact. If it happens, it's along the lines of the abandoned-for-lack-of-interest #116.

[eparis]

Is there any chance this makes us have to block edges later? I can't think of a reason... So I think I like this PR.

[sdodson]

Yes we could end up having to block edges later. But edge blocks aren't channel bound so if 4.3.12 to 4.3.13 or 4.3.12 to 4.4.0 were blocked it'd also be blocked here as well.

The primary motivation here is to land releases before console starts letting people choose 4.4 channels so that if someone were to change before we had minor version upgrades we wouldn't orphan them. For instance, I attempted to go from 4.1.0 to 4.2, the biggest upgrades I could take were 4.1.0 to 4.1.14 to 4.1.25 at which point the console let me switch to stable-4.2 and I could no no where.

Maybe I misunderstood the question though.

[sdodson]

Merge conflicts on our insistence to drop metadata in channel files. I'll rebase.

[sdodson]

/assign @jottofar
This errata is shipping today.

[jottofar]

/unhold

[jottofar]

/lgtm

[jottofar]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: jottofar, vfreex

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• channels/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sdodson]

I've set approved label so this merges, we'd previously agreed that OTA can add items to channels without architect approval but we've not taken action on #173 so that's not possible.