Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to 8.13. #12346

Merged
merged 1 commit into from
May 18, 2020
Merged

Update to 8.13. #12346

merged 1 commit into from
May 18, 2020

Conversation

Zimmi48
Copy link
Member

@Zimmi48 Zimmi48 commented May 18, 2020

Part of this PR was automatically generated by running dev/doc/update-compat.py --master.

Kind: infrastructure.

@Zimmi48 Zimmi48 added the kind: infrastructure CI, build tools, development tools. label May 18, 2020
@Zimmi48 Zimmi48 added this to the 8.13+beta1 milestone May 18, 2020
@Zimmi48 Zimmi48 requested review from a team as code owners May 18, 2020 09:30
@Zimmi48 Zimmi48 requested a review from a team May 18, 2020 09:30
@Zimmi48 Zimmi48 requested review from a team as code owners May 18, 2020 09:30
@ejgallego ejgallego self-assigned this May 18, 2020
@Zimmi48
Copy link
Member Author

Zimmi48 commented May 18, 2020

@JasonGross There seems to be the usual business that needs your attention regarding fiat-parsers. (BTW, would there be a way to anticipate this for you?)

Part of this PR was automatically generated by running dev/doc/update-compat.py --master
@ejgallego
Copy link
Member

@Zimmi48 , proposed tag for 8.13+alpha is f123874 , branching point is b456cf6

@ejgallego
Copy link
Member

@JasonGross There seems to be the usual business that needs your attention regarding fiat-parsers. (BTW, would there be a way to anticipate this for you?)

Indeed @JasonGross you could maybe do 8.13, 8.14, 8.15 :)

@ejgallego
Copy link
Member

By the way I rebased as to get a more linear history.

@gares gares mentioned this pull request May 18, 2020
39 tasks
@Zimmi48 Zimmi48 deleted the bump-8.13 branch May 18, 2020 16:57
@JasonGross
Copy link
Member

I've updated fiat. I've also added a script to coq-scripts that will automatically update the compatibility versions as necessary. I've also reduced the number of manual changes that need to be made. However, there are still some things that I don't want to do too early:

  • When Coq.Compat.Coq811 stops existing, I'll need to update the my scripts to pull in a different compat file, and perhaps manually copy/paste the contents into my own compat files (at some point, I should probably simplify the build system of fiat, and also remove compat hacks that aren't needed)
  • I don't want to create version-specific copies of the .ml files in fiat. If it doesn't recognize the version, it's just a warning, and it defaults to the 8.12 version of the files. And if I create them early, then every change to the relevant ml interfaces will need to change not just the .813 ml files, but also the .814, .815, etc, for all the not-yet-created versions.

@ejgallego
Copy link
Member

Thanks @JasonGross

Zimmi48 added a commit to Zimmi48/coq-elpi that referenced this pull request Jan 26, 2021
Zimmi48 added a commit to Zimmi48/QuickChick that referenced this pull request Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: infrastructure CI, build tools, development tools.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants