Skip to content

Document the Haskell Language Server versioning policy #1434

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.

Sign up for GitHub

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

Jump to bottom
Closed
pepeiborra opened this issue Feb 24, 2021 · 2 comments
Closed

Document the Haskell Language Server versioning policy #1434

pepeiborra opened this issue Feb 24, 2021 · 2 comments
Labels
status: in discussion Not actionable, because discussion is still ongoing or there's no decision yet type: enhancement New feature or request

Comments

@pepeiborra
Copy link
Collaborator

pepeiborra commented Feb 24, 2021 •
edited
Loading

It's clearly not the PVP, so it ought to be documented somewhere for the sake of future contributors and maintainers.

The documentation should include answers for the following questions:

  1. Motivation for deviating from the PVP, and tradeoffs
  2. Specification: lower bounds, upper bounds, and version bumps, for all the categories of packages.
    There are 3 categories imho:
    1. core packages
    2. plugin packages
    3. the HLS package
  3. Examples of releases that involve interactions with Hackage:
    1. Major release
    2. Bug fix release for core packages
    3. Bug fix release for plugin packages
    4. Bug fix release for HLS
@Ailrun Ailrun added the status: in discussion Not actionable, because discussion is still ongoing or there's no decision yet label Feb 26, 2021
@jneira jneira mentioned this issue Apr 12, 2021
Closed
@jneira
Copy link
Member

jneira commented May 5, 2021

We are following pvp almost strictly in practice, not sure if it still is needed to document it somewhere

@pepeiborra
Copy link
Collaborator Author

That's great news, will close then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: in discussion Not actionable, because discussion is still ongoing or there's no decision yet type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pepeiborra @jneira @Ailrun