Che: Figure out versioning/release info for devworkspace controller and WTO

[amisevsk]

Is your task related to a problem? Please describe.

We should decide on a branch/tag structure for devworkspace-operator/web-terminal-operator releases. Currently, we have the v1.0.0-alphax branch of devworkspace-operator, and the v1.0.x branch of web-terminal-operator. However, these versions aren't reflected in files within the repo:

• version.go in devworkspace operator is v0.0.1 for both master and the v1.0.0-alphax branches
• the web-terminal-operator lists version 1.0.0 in both the master and v1.0.x branches.

Additionally, both 'release' branches are v..x, and there are no tags in either repo to signify which commit in the branch is the v1.0.0-alpha1 or v1.0.0 release.

Describe the solution you'd like

• Create tags at current v1.0.* branch HEADs to tag releases
• Include updated version info with repo files for both repos

Additional info

Version numbers for the currently released and next version are consumed to generate automatic backlogs from multiple sources. The version numbers for WTO should match releases in the Jira backlog.

[amisevsk]

cc: @benoitf

[sleshchenko]

Good catch!

[sleshchenko]

I think the tags are not created mainly due fact that we still change some code.
About version.go in the X branches and in master - they should be aligned for sure.

[sleshchenko]

devworkspace operator has v1.0.0-aplha1 tag and 1.0.0-next in version.go. Is it going to help to automated tools or we need like v1.0.0-alpha2-snapshot in version.go?

web terminal operator now has https://github.com/redhat-developer/web-terminal-operator/releases/tag/v1.0.1 which is most closest to released on http://pkgs.devel.redhat.com/cgit/containers/web-terminal-dev-operator-metadata/commit/?h=web-terminal-1.0-rhel-8&id=d8b1423d8d8334b87cb6645e54d08e10f6403e28
https://github.com/redhat-developer/web-terminal-operator/blob/v1.0.x/Dockerfile#L53 contains the next z stream version.

@amisevsk @JPinkney any ideas what can be done more in the scope of this issue?

[benoitf]

it might not be enough from .go files.

Note that some che repos have a VERSION file where the current version is defined and this file is used by the job that do the release. (so it can be triggered easily)

example https://github.com/eclipse/che-machine-exec/blob/master/VERSION

[sleshchenko]

In addition it makes sense to put versions into https://github.com/redhat-developer/web-terminal-tooling (no version) and https://github.com/redhat-developer/web-terminal-exec/tree/v1.0.x (7.17.0-SNAPSHOT
version from upstream)