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.

Sign up for GitHub

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

Jump to bottom

Post release tasks for 4.8.1 #1445

Closed
10 tasks done
davidjiglesias opened this issue Jul 18, 2024 · 1 comment · Fixed by #1446, #1447, #1448, #1449 or #1450
Closed
10 tasks done

Post release tasks for 4.8.1 #1445

davidjiglesias opened this issue Jul 18, 2024 · 1 comment · Fixed by #1446, #1447, #1448, #1449 or #1450
Assignees
@davidcr01
Labels
level/subtask Task issue request/operational Operational requests type/maintenance

Comments

@davidjiglesias
Copy link
Member

davidjiglesias commented Jul 18, 2024 •
edited by davidcr01
Loading

Description

This issue attempts to track the steps necessary to complete post-release maintenance tasks for 4.8.1.
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.8.1-into-4.9.0.

Tasks

  • Merge branch 4.8.1 into branch 4.9.0.
  • Merge branch 4.9.0 into branch master.
  • Publish GitHub release as latest.
  • Delete all stage pre-releases for 4.8.1 (https://github.com/wazuh/wazuh-docker/releases).
  • Delete all stage tags for v4.8.1. BE CAREFUL NOT TO DELETE DEFINITIVE TAG. Example: v4.8.1-rc1, 4.8.1-alpha1, etc.
  • Update Docker hub readme compatibility matrix to include 4.5.3 for manager, dashboard, and indexer.
  • Delete all stage Docker hub images for v4.8.1. BE CAREFUL NOT TO DELETE DEFINITIVE DOCKER IMAGES. Example: v4.8.1-rc1, 4.8.1-alpha1, etc.

Extra tasks

  • Revert "Merge branch 4.9.0 into branch master".
  • Merge branch 4.9.0 into branch 4.10.0.
  • Merge branch 4.10.0 into branch master.
@davidjiglesias davidjiglesias mentioned this issue Jul 18, 2024
Open
5 tasks
@davidcr01 davidcr01 mentioned this issue Jul 18, 2024
Merged
@davidcr01 davidcr01 linked a pull request Jul 18, 2024 that will close this issue
Merge 4.8.1 into 4.9.0 #1446
Merged
@davidcr01 davidcr01 mentioned this issue Jul 18, 2024
Merged
@davidcr01 davidcr01 linked a pull request Jul 18, 2024 that will close this issue
Merge 4.9.0 into master #1447
Merged
@davidcr01 davidcr01 reopened this Jul 18, 2024
@davidcr01 davidcr01 mentioned this issue Jul 18, 2024
Merged
@davidcr01 davidcr01 linked a pull request Jul 18, 2024 that will close this issue
Updated files of README.MD #1448
Merged
This was referenced Jul 18, 2024
Merged
Merged
This was linked to pull requests Jul 18, 2024
Merge 4.8.1 into 4.9.0 #1449
Merged
Merge 4.9.0 into master #1450
Merged
@davidcr01 davidcr01 reopened this Jul 19, 2024
@davidcr01
Copy link
Contributor

It is necessary to revert the merge of 4.9.0 into master because we need to bump 4.9.0 into 4.10.0, and then, 4.10.0 into master.

@davidcr01 davidcr01 mentioned this issue Jul 19, 2024
Merged
@davidcr01 davidcr01 linked a pull request Jul 19, 2024 that will close this issue
Revert merges of 4.9.0 branch into master branch #1451
Merged
This was referenced Jul 19, 2024
Merged
Merged
@davidcr01 davidcr01 linked a pull request Jul 19, 2024 that will close this issue
Merge 4.10.0 into master #1459
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidcr01 davidcr01

Labels
level/subtask Task issue request/operational Operational requests type/maintenance
Projects
Release 4.8.1
Status: Done
Milestone
No milestone
3 participants
@davidjiglesias @c-bordon @davidcr01