Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SRVLOGIC-258] Remove tech-preview string from productized images #23

Merged
merged 1 commit into from
Mar 20, 2024

Conversation

rgdoliveira
Copy link
Member

@rgdoliveira rgdoliveira commented Mar 20, 2024

Jira: https://issues.redhat.com/browse/SRVLOGIC-258

Note: PR for kiegroup/kogito-serverless-operator will be created later.

How to retest this PR or trigger a specific build:
  • (Re)run Jenkins tests
    Please add comment: Jenkins [test|retest] this
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Copy link
Member

@ricardozanini ricardozanini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this 1 in openshift-serverless-1?

@rgdoliveira
Copy link
Member Author

rgdoliveira commented Mar 20, 2024

Why do we need this 1 in openshift-serverless-1?

AFAIK this is the stream (like Serverless 1.x), we are using this since the begging and following what Serverless team is doing.

@rgdoliveira rgdoliveira merged commit 6cd1628 into kiegroup:main Mar 20, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants