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

Maintain production and numbered branches post release 4.5.1 in wazuh-qa repository #4456

Closed
6 tasks done
davidjiglesias opened this issue Aug 24, 2023 · 4 comments · Fixed by #4457, #4458, #4459 or #4460
Closed
6 tasks done

Comments

@davidjiglesias
Copy link
Member

davidjiglesias commented Aug 24, 2023

Description

The goal is to complete the following tasks, each task must have a PR associated with this issue.

The branches must follow the naming: merge-<ORIGIN_BRANCH>-into-<DESTINATION_BRANCH>. For example, merge-4.5.1-into-4.5.2.

Tasks

  • Merge branch 4.5.1 into branch 4.5.2 on wazuh-qa repository.
  • Merge branch 4.5.2 into branch 4.6.0 on wazuh-qa repository.
  • Merge branch 4.5.2 into branch 4.6.0 on wazuh-qa repository (bis). Merge 4.5.2 into 4.6.0 #4469
  • Merge branch 4.6.0 into branch 4.7.0 on wazuh-qa repository.
  • Merge branch 4.6.0 into branch 4.7.0 on wazuh-qa repository Merge 4.6.0 into 4.7.0 #4470
  • Merge branch 4.7.0 into branch master on wazuh-qa repository.
@damarisg damarisg self-assigned this Aug 24, 2023
@damarisg damarisg linked a pull request Aug 24, 2023 that will close this issue
This was referenced Aug 24, 2023
@damarisg damarisg linked a pull request Aug 24, 2023 that will close this issue
@damarisg damarisg linked a pull request Aug 24, 2023 that will close this issue
@damarisg damarisg linked a pull request Aug 24, 2023 that will close this issue
@jnasselle
Copy link
Member

Reopening this due to repos missing alignment on PRs merges

@jnasselle jnasselle reopened this Aug 25, 2023
@jnasselle
Copy link
Member

@jnasselle
Copy link
Member

jnasselle commented Aug 25, 2023

@Rebits
Copy link
Member

Rebits commented Aug 28, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment