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

[KIECLOUD-656] - Prepare RHPAM branches for 7.13.2 #840

Merged
merged 1 commit into from
Dec 13, 2022

Conversation

spolti
Copy link
Member

@spolti spolti commented Dec 4, 2022

Signed-off-by: spolti fspolti@redhat.com

Signed-off-by: spolti <fspolti@redhat.com>
@sonarcloud
Copy link

sonarcloud bot commented Dec 4, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@spolti spolti requested review from rgdoliveira and removed request for ruromero December 4, 2022 20:19
@rgdoliveira
Copy link
Member

@spolti shouldn't this PR be opened against release-v7.13.x branch instead of main? Or you will backport it later?

@spolti
Copy link
Member Author

spolti commented Dec 5, 2022

@spolti shouldn't this PR be opened against release-v7.13.x branch instead of main? Or you will backport it later?

no, main is 7.13.2.

@rgdoliveira
Copy link
Member

@spolti shouldn't this PR be opened against release-v7.13.x branch instead of main? Or you will backport it later?

no, main is 7.13.2.

I'm confused, when we build the BA operator we checkout to branch release-v7.13.x, isn't it @lampajr ?

@spolti
Copy link
Member Author

spolti commented Dec 5, 2022

@spolti shouldn't this PR be opened against release-v7.13.x branch instead of main? Or you will backport it later?

no, main is 7.13.2.

I'm confused, when we build the BA operator we checkout to branch release-v7.13.x, isn't it @lampajr ?

yes, 7.13.x is pointing to 7.13.1-2 atm.

@rgdoliveira
Copy link
Member

@spolti shouldn't this PR be opened against release-v7.13.x branch instead of main? Or you will backport it later?

no, main is 7.13.2.

I'm confused, when we build the BA operator we checkout to branch release-v7.13.x, isn't it @lampajr ?

yes, 7.13.x is pointing to 7.13.1-2 atm.

I see, so for release-v7.13.x branch you will add the 7.13.2-1 OLM, right?

@spolti
Copy link
Member Author

spolti commented Dec 5, 2022

@spolti shouldn't this PR be opened against release-v7.13.x branch instead of main? Or you will backport it later?

no, main is 7.13.2.

I'm confused, when we build the BA operator we checkout to branch release-v7.13.x, isn't it @lampajr ?

yes, 7.13.x is pointing to 7.13.1-2 atm.

we will merge main into 7.13.x before the 7.13.2 release and open the main branch for 7.13.3 development cycle.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 5, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: desmax74, rgdoliveira, spolti

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@spolti spolti merged commit c9c8f5d into kiegroup:main Dec 13, 2022
@spolti spolti deleted the KIECLOUD-656 branch December 13, 2022 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants