-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Labels
changelog:new-featureChange that should be called out as new feature in CHANGELOGChange that should be called out as new feature in CHANGELOGenhancementgood first issueGood for beginnersGood for beginnershelp wantedFeatures that maintainers are willing to accept but do not have cycles to implementFeatures that maintainers are willing to accept but do not have cycles to implement
Description
Requirement
We would like to simplify the release process.
Problem
Right now the release involves a number of manual steps, e.g. in the second section of this issue: #7496
Proposal
Similar to jaegertracing/jaeger-ui#3056, automate the manual steps:
- automate creation of PR with changelog and UI upgrade
- automate pushing tags (print commands to be executed for user to confirm)
The last two steps (creating release and kicking off artifacts building workflow) can remain manual for now.
The overall release process would be:
- run
release/start.sh
which creates a PR with instructions / steps similar to Prepare Jaeger Release v1.73.0 / v2.10.0 #7496. In those instructions all versions should be pre-populated already, because start.sh determines them. - in the issue checklist the automated command for creating release would be something like "Run:
bash ./scripts/release/prepare 1.x.x 2.x.x
(with concrete versions).
Metadata
Metadata
Assignees
Labels
changelog:new-featureChange that should be called out as new feature in CHANGELOGChange that should be called out as new feature in CHANGELOGenhancementgood first issueGood for beginnersGood for beginnershelp wantedFeatures that maintainers are willing to accept but do not have cycles to implementFeatures that maintainers are willing to accept but do not have cycles to implement