Skip to content

Conversation

@sdodson
Copy link
Member

@sdodson sdodson commented Jul 27, 2021

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 27, 2021
@LalatenduMohanty
Copy link
Member

/hold till errata is public
/lgtm

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 27, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2021
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2021
@LalatenduMohanty
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 27, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, sdodson

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:
  • OWNERS [LalatenduMohanty,sdodson]

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

@wking
Copy link
Member

wking commented Jul 27, 2021

e2e:

Error: Error in channel ordering: ["Release 4.8.2 present in stable-4.8, but not in fast-4.8"]

/retest

@sdodson
Copy link
Member Author

sdodson commented Jul 27, 2021

/retest

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 27, 2021
sdodson added 3 commits July 27, 2021 19:57
fast-4.8 starts getting everything from candidate-4.8
stable-4.8 filters for 4.8 versions
GA is special case going immediately into the stable channel
without any upgrade edges
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 27, 2021

New changes are detected. LGTM label has been removed.

@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 27, 2021
@sdodson sdodson added the lgtm Indicates that a PR is ready to be merged. label Jul 28, 2021
@sdodson
Copy link
Member Author

sdodson commented Jul 28, 2021

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 28, 2021
@openshift-merge-robot openshift-merge-robot merged commit 255190a into openshift:master Jul 28, 2021
@sdodson sdodson deleted the 48-ga-changes branch July 28, 2021 00:11
wking added a commit to wking/cincinnati-graph-data that referenced this pull request Sep 3, 2021
When we have a GitHub token, we checkout a branch and create a pull
request for each promotion.  When we don't have a token, we used to
just log the changes that needed to happen.  With this commit, a
token-less call will now edit the local files to perform all
appropriate promotions.  That allows this script (which understands
about tombstones and filters and other promotion criteria) to be used
to backfill channels when we expand filters (e.g. allowing 4.(y-1) in
fast-4.y after 4.y GAs, or allowing 4.(y-1) in stable-4.y after we
feel comfortable with the fast behavior.  That should make things like
8da5782 (4.8 GA -- Fill in 4.7.z into fast-4.8, 2021-07-26, openshift#947)'s
accidental promotion of the tombstoned 4.7.10 and similar less likely.
More on that in 4c53c7b (Blocking all the incoming edges to 4.7.10,
4.7.14, 4.7.15, 4.7.20, 2021-09-03, openshift#1035).

Drop the old backfill script from 2a02325 (hack/backfill: Add a
backfilling script, 2020-11-12, openshift#549), now that this new functionality
makes it obsolete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants