[release-1.6] Tag 1.6.2

[mtrmac]

No description provided.

[mtrmac]

@lsm5 @jnovy FYI. (The release should be tagged in the middle of this PR.)

[lsm5]

I think the release branch itself with the backported commit would suffice for @jnovy's needs. But, I'm cool either way. LGTM.

[rhatdan]

I did not think we did -dev tags in released branches?

[jnovy]

good catch @rhatdan ! Yes please, no -dev in version for maintenance branches @mtrmac

[mtrmac]

It’s quite possible, in that case I’m just unaware of that convention. In the Skopeo context, historical practice varies.

(I think some marker to make sure the 1.6.2 release is unambiguous, even if we latter use the branch, is valuable. I don’t care about the particular name, if -dev is perceived to imply there is active development going on on that branch; it could be -unreleased or -release-branch or whatever.)

[mtrmac]

@jnovy After this PR, there would be a version v1.6.2 tagged either way.

This would only affect about the version reported in any future cherry-pick, if it happened without tagging a post-v1.6.2 release. From the upstream perspective, it is valuable to be able to differentiate the “real” v1.6.2 from a cherry-pick of a different tree.

[jnovy]

@mtrmac "-maint" could do if you prefer a tag to be added to the maintenance branch IMO.

[rhatdan]

I think it is fine to leave it, but we almost always do a back port and cut a release. We don't have long lasting changes to a release branch.

[mtrmac]

Updated the post-release version to 1.6.2-maint.

[lsm5]

LGTM

[mtrmac]

Merging so that this doesn’t block packaging work; we can adjust the post-release name later.

[mtrmac]

https://github.com/containers/skopeo/releases/tag/v1.6.2