[Issue]: Tag previous versions

[jo-mueller]

Describe the issue

I think to have a clean build structure in the future, it will be easier to have the tagging here become the central place from which to manage releases. See also ome/ngff#581

This requires us to tag all the old versions, so that the enum of existing versions and the respective schemas are easily findable from this repo (i.e. via git ls-remote --tags https://github.com/ome/ngff-spec)

This means we need to find the times/dates when previous versions were released, which we can take from the ngff version history

• 0.5: 2024-11-21
• 0.4: 2022-02-08
• 0.3: 2021-08-24
• 0.2: 2021-03-29
• 0.1: 2020-04-20

@joshmoore @sbesson any objections?

[sbesson]

Another possible source of truth could be the tags on the ngff repository is https://github.com/ome/ngff/tags, many of these were pushed a posteriori but the time of the underlying commits are:

Tag	commit	Date
0.1.0	ome/ngff@c6d7d84	2020-11-20
0.2.0	ome/ngff@bba6940	2021-04-26
0.3.0	ome/ngff@47fa3dc	2021-08-24
0.4.0	ome/ngff@0f03373	2022-02-08
0.5.0	ome/ngff@8a0f886	2024-11-25

These are largely consistent with the dates recorded in the version history

[jo-mueller]

Since this touches the work at ome/ngff#581 , I will discuss a bit more with @lubianat to see how we could build this according to our needs.

[joshmoore]

All the commits that are tagged in the ngff repo also exist in the ngff-spec repo:

for tag in $(git -C ngff tag -l); do
>     commit=$(git -C ngff rev-list -n 1 "$tag")
>
>     if git -C ngff-spec cat-file -e "$commit^{commit}" 2>/dev/null; then
>         echo "YES  $tag  $commit"
>     else
>         echo "NO   $tag  $commit"
>     fi
> done
YES  0.0.1  4cc253528fdab39e2b4e534fda15099f61636b99
YES  0.1.0  c6d7d84f77959846ecdc9b65eecfa87bb6dc1f86
YES  0.1.3  37f0223549adb79315760608796fcdaba7ae1bc3
YES  0.2.0  bba6940f524345f3b4dd1d856a463a968ad73fd9
YES  0.3.0  47fa3dc9d478f5418204b8eb17d09454bd9af2aa
YES  0.4.0  0f03373888f3103978843d5d0a896521807f2637
YES  0.4.1  106c3010dcb4079eb0a69868a11cc5943f942fdf
YES  0.5.0  8a0f886aac791060e329874b624126d3530c2b6f
YES  0.5.1  5ecd8371a8833b27a414cf205cc56a4af458fc84
YES  0.5.2  5cdf83b6806b5e500477c7af69dae9ed2adcf77d

So I think what you want, @jo-mueller, is (A) that those get pushed to the ngff-spec repo (mea culpa) and (B) that one or more tags get created on each of the branches to represent the newest state.

I will take care of (A) if there are no objections (👎🏽) and I'd suggest we do (B) as a PR against each of the branches to update the changelog, the README, etc. which when approved we merge and release as the latest tag.