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

New versioning scheme. #400

Closed
ejgallego opened this issue Mar 20, 2024 · 1 comment
Closed

New versioning scheme. #400

ejgallego opened this issue Mar 20, 2024 · 1 comment
Milestone

Comments

@ejgallego
Copy link
Owner

After some thinking, I have decided to implement the coq-lsp versioning model for Coq SerAPI. This has a lot of advantages, in particular w.r.t. change tracking.

That means that we will have a single SerAPI version, supporting several Coq versions.

Problem is that we need to move from a scheme where version numbers are 8.19.0+0.19.1 to a scheme where the SerAPI version is first. We could bump the epoch, but as SerAPI is being put in maintenance mode, I think for 8.20 I will provide a coq-serlib package that can be versioned like that, and maybe keep coq-serapi version working as now.

@ejgallego ejgallego added this to the 0.20.0 milestone Mar 20, 2024
@ejgallego
Copy link
Owner Author

Finally this won't be implemented, we have moved to this model in coq-lsp with #409

@ejgallego ejgallego closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant