v2.0.0-alpha tag is not found in the main branch so "git describe" still returns the delta from v1.0.0-rc

Value

In our whole compliance workflow, meaningfully tagging each scanned project snapshot is fundamental. Up to now, we used the output of git describe command on the Oniro repo because it returns the delta from the latest release, like in v1.0.0-rc-341-gf16bce7 (which means commit f16bce7, 341 commits ahead of v1.0.0rc release).

However, since the latest v2.0.0-alpha tag points to a commit outside the main branch, even after the alpha release we are still getting project snapshot tags like v1.0.0-rc-375-g57ddacd. This breaks our whole tagging system, which is crucial in our workflow, because we use such tags to tag each and every component, to understand which release/snapshot it belongs to.

Acceptance Criteria

v2.0.0-alpha tag should belong to the main branch. Or at least the new v2.0.0-alpha2 tag should (if we decide to solve issue #616 (closed) in such way)

Applicable Personas

• License Compliance Auditor

added goofyalpha label

assigned to @landgraf

added to epic &95 (closed)

changed the description

marked this issue as related to #616 (closed)

There's tag 2.0.0-alpha in the project https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/tags/v2.0.0-alpha I've pushed it directly with git push because of chicken-egg problem (CI needs tags, tags need CI). But gitlab decided that MR !131 (merged) has been merged and replaced tagged commit with the one from MR (which supposed to be tagged as well).

as discussed v2.0.0-alpha2 is in the repo

closed

changed milestone to %goofy alpha

changed iteration to Oniro Core Iterations Jun 1, 2022 - Jun 30, 2022

set weight to 1

removed goofyalpha label

added teamipcompliance label

added teammaintenance label and removed teamipcompliance label