git tags for releases

[antoinerg]

For practical reasons, it has been decided a little while ago that we would decouple releases for on-prem and desktop users because of their vastly different release process:

• on-prem (which simply amounts to publishing a Docker image)
• desktop users (multiple installation methods, multiple artifacts published at different services, meant for multiple operating systems, much longer QA process)

I think this decision has been a good one since it greatly relieves pressure on Orca maintainers from doing tedious release/QA each time a minor fix meant for on-prem needs to be published.

However, we currently have a problem with our git tags naming schema. We have git tags with version numbers tied to on-prem release with format vX.Y.Z (currently in the v3) and git tags that are semantically versioned using the same format vX.Y.Z tied to our open-source/desktop releases (currently in the v1). To my knowledge, we haven't made any breaking changes so Orca releases for the open-source/desktop community should remain in v1.

Moving forward, the git tags tied to on-prem releases should probably contain an on-prem string in them in order to distinguish them. Our CircleCI config should also be updated to reflect that change.

cc @joaoalf @plotly/devops

[etpinard]

Moving forward, the git tags tied to on-prem releases should probably contain an on-prem string in them in order to distinguish them

:+1:

like this one https://github.com/plotly/orca/releases/tag/v1.0.1-onprem