Please create a tag for Coq 8.16 in Coq Platform 2022.09

[MSoegtropIMC]

The Coq team released Coq 8.16+rc1 on June 01, 2022.
The corresponding Coq Platform release 2022.09 should be released before September 15, 2022.
It can be delayed in case of difficulties until October 15, 2022, but this should be an exception.

This issue is to inform you that to our (possibly a few days old) best knowledge the latest released version of your project (1.3.2+8.15) does not work with Coq 8.16+rc1.
We tried to remove version restrictions in opam files and possibly make or configure files, but this did not suffice.

Please note that in Coq Platform CI (unlike Coq CI) we test only released / tagged versions. Coq CI appears to test this project, but has some special handling for your project which makes it difficult to retrieve the commit it tests for your project.

Could you please create a tag and opam package, or communicate us any existing tag that works with Coq branch v8.16, preferably before August 31, 2022?
In case we might have to delay the Coq Platform release cause of issues with your project, we would prefer to be informed about the situation as early as possible.

In case the tag and opam package are available before August 17, 2022, it will be included in an early Coq Platform beta release of the for Coq 8.16+rc1.

The working branch of Coq Platform, can be found here main.
It contains package pick ~8.16+rc1~2022.09~preview1 which already supports Coq version 8.16+rc1 and contains already working (possibly patched / commit pinned) Coq Platform packages.

Please don't close this issue, even after creating the new tag and/or opam package.
We will close the issue after updating Coq Platform.
This is a measure of 'double book keeping' in order to avoid that we ship the wrong version.

In any case, Coq Platform won't be released before this issue is closed!

Thanks!

P.S.: this issue has been created automatically based on CI status.

CC: coq/platform#274

[lukaszcz]

The v1.3.2 release for Coq 8.16 has been created (branch v1.3.2-coq8.16)

[SnarkBoojum]

Can I ask you to tag the same commit 09f5ffa as v1.3.2-coq8.16 in addition to the existing tag v1.3.2+8.16 ? You have incoherent numbering, and that makes it more difficult to auto-detect new releases, see the list of tags [Notice the two changes: - vs + and coq or not]

Thanks!

[lukaszcz]

This change to +8.16 was intentional and I intend to keep it in the future to avoid having branches and tags with the same name.

Can you just change your way of detecting new releases to use the new tag name format?

[SnarkBoojum]

Ah, if it's deliberate and intended for long-term, I definitely can adapt. Thanks!

[MSoegtropIMC]

@lukaszcz : can you next time please leave the issue open until I updated Coq Platform (as requested in the text). I need this for book keeping to ensure I don't forget anything (just found this in double checking).

[MSoegtropIMC]

I updated coq-hammer to v1.3.2-coq8.16 and z3_tptp to version 4.11.0.

[lukaszcz]

Ok, sorry, didn't read the text carefully enough

…

On Tue, 13 Sep 2022, 18:02 MSoegtropIMC, ***@***.***> wrote: @lukaszcz <https://github.com/lukaszcz> : can you next time please leave the issue open until I updated Coq Platform (as requested in the text). I need this for book keeping to ensure I don't forget anything (just found this in double checking). — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPKH4KRUKVNYCRQYYFA5TV6CQPRANCNFSM56ENPUUA> . You are receiving this because you were mentioned.Message ID: ***@***.***>