-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Bump current minor numbered branches (4.5+) #17639
Labels
Comments
7 tasks
This was referenced Jun 23, 2023
Merged
This was referenced Jun 23, 2023
This was referenced Jun 23, 2023
This was referenced Jun 26, 2023
7 tasks
7 tasks
5 tasks
This was referenced Jul 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This issue attempts to bump current 4.5 and master(4.6) to 4.6.0 and master(4.7.0) respectively. The reasoning behind it is to create a space to introduce 4.5.0 with the NVD API 2.0 development.
CRITICAL NOTICE
Each step from below must be thoroughly completed before the next one can be tackled
Tasks (For all repositories)
Bump version in master branch to version 4.7.0 and add a changelog entry
Use a script to rename version in release field in the team projects from 4.6.0 to 4.7.0
Ensure all issues from 4.6.0 are already in 4.7.0 and included in the new release project (4.7.0)
Rename branch 4.5 to 4.6.0
The jenkins rename failed and we cannot delete the 4.5 branch.
Bump version in 4.5 branch version to 4.6.0 and add a changelog entry
Use a script to rename version in release field in the team projects from 4.5.0 to 4.6.0
Ensure all issues from 4.5.0 are already in 4.6.0 and included in the new release project (4.6.0)
Create branch 4.5.0 using tag v4.4.4 as base
Bump version in 4.5.0 branch to version 4.5.0 and add a changelog entry
Open v4.5.1 release issue in wazuh/releases https://github.com/wazuh/releases/issues/7
Create Release 4.5.1 project in wazuh https://github.com/orgs/wazuh/projects/56
Rename 4.4.5 to 4.5.1, if your repository does not currently have 4.4.5 or any development for that version, create 4.5.1 branch from 4.5.0. Bump version in 4.5.1 branch to version 4.5.1 and add a changelog entry.
Use a script to rename version in release field in the team projects from 4.4.5 to 4.5.1
Ensure all issues from 4.4.5 are already in 4.5.1 and included in the new release project (4.5.1)
All AWS resources should be regenerated using the
Procedure_ecs_task_tier
pipeline on branches that have been modified/bumpedThe text was updated successfully, but these errors were encountered: