Create a template / checklist for Jaeger release

[yurishkuro]

When we do a new release of Jaeger, the maintainer has to follow the relatively lengthy process documented in the RELEASES.md. The instructions are somewhat complicated, sometimes it is easy to forget a step. What if instead we had a script like start-release.sh that would:

• automatically determine the next release numbers
• create a new issue with the appropriate title and a checklist of steps for the maintainer to execute (e.g. by copying it from the RELEASES.md, assuming we adjust the formatting a bit, such as by changing bullets to * [ ] ... so that they are rendered as checkboxes on the GitHub issue).

This way the maintainer could be executing the steps from the issue rather than the RELEASES.md doc and ticking off boxes as they do it.

[ADI-ROXX]

automatically determine the next release numbers

For solving this issue, I have the following methodology in mind:

1. Following is a command that tells the current version

In the start-release.sh, I want to take the input of a flag --type that takes the following values: [mini, mid, high] that will have the following aspects:

• mini: v2.3.0 -> 2.3.1
• mid: v2.3.0 -> 2.4.0
• high: v2.3.0 -> 3.0.0

Is this logic correct?

[yurishkuro]

Current versions can be determined with "make echo-v1|v2". We always bump minor version, no need for additional parameters, but the script can prompt the user for the next version with an automated default value.

[ADI-ROXX]

but the script can prompt the user for the next version with an automated default value.

I am thinking of the following:

When we run start-release.sh, it will show the next version and ask for confirmation from the user.

Is this method correct?

[yurishkuro]

Yes but it should be simpler - prompt user for the next version but suggest a viable default (next minor) such that the user only needs to press ENTER in most cases.

[ADI-ROXX]

You mean like this:

[ADI-ROXX]

create a new issue with the appropriate title and a checklist of steps for the maintainer to execute (e.g. by copying it from the RELEASES.md, assuming we adjust the formatting a bit, such as by changing bullets to * [ ] ... so that they are rendered as checkboxes on the GitHub issue)

@yurishkuro The checklist has to be copied from Jaeger Backend Release Process in Release.md right:

Or do I have to include the Jaeger Overall Release or Patch Release also:

[yurishkuro]

we need backend release, UI release, and documentation release.

[ADI-ROXX]

create a new issue with the appropriate title and a checklist of steps for the maintainer to execute (e.g. by copying it from the RELEASES.md, assuming we adjust the formatting a bit, such as by changing bullets to * [ ] ... so that they are rendered as checkboxes on the GitHub issue).

When you say "copying," do you mean to manually copy the data from release.md to the start-release.sh (kind of hard-code start-release.sh) or do you mean that the script should automatically do the copying?

[yurishkuro]

automatically, into the ticket body