Closed palmskog closed 2 years ago
I agree. What's the timeline for this? I have seen that 8.15_rc1
has been tagged, but I haven't seen any "please choose your version" issues yet. I'm still confused as to whether packages should preferably release as soon as x_rc1
is tagged or wait until x.0
is tagged.
Here is how I personally view the processes, based on discussion with the people involved:
extra-dev
(if necessary), enabling others that depend on them to test with 8.XY+rc1.extra-dev
migrate to released
.So the bottom line: we can tag and release 1.1.3 as soon as we have tested with 8.15+rc1, but we can also wait with tagging until Platform maintainers open an issue about the 8.15 platform release.
Well, AFAIK there has not yet been any conclusion on how to deal with this in mathcomp, and I don't think it makes sense to tag directly before mathcomp. I'll put the discussion on the platform release process on agenda of the next mathcomp meeting. Feel free to join this meeting.
I'll also try and schedule some time to make another pass over #37
OK, I can join the next MC meeting (looks like it's Jan 12?).
@chdoc OK to add coq-platform
tag/topic to the reglang repo? It's convenient to track which projects here are in the Platform.
Sure, go ahead! :+1:
To make it official, we now aim to release version 1.1.3 of RegLang after we have confirmed it works with MathComp 1.14.0, to be released week of Jan 17, 2022.
I propose that for the Coq platform release with Coq 8.15, we make RegLang release 1.1.3 that supports MathComp 1.11 or later (i.e., including content of #37). This release can then be the basis of a release of Regexp Brzozowski, which was recently ported to use RegLang. I'm opening this issue as a memento.