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.

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

Release planning #237

Closed
alanz opened this issue Mar 20, 2020 · 2 comments · Fixed by #238
Closed

Release planning #237

alanz opened this issue Mar 20, 2020 · 2 comments · Fixed by #238
Assignees
@alanz

Comments

@alanz
Copy link
Collaborator

alanz commented Mar 20, 2020

We have had a number of changes land recently, I think we should make a new release.

My thinking is to do it with the current state, and let #234 land in a later one, so people can experiment with it from master initially.

This allows the benefits of current improvements/bug fixes without having to change downstream code too much.

Thoughts?

cc @cocreature @bubba
@cocreature
Copy link
Contributor

Making a release without #234 sounds great 👍

@lukel97
Copy link
Collaborator

lukel97 commented Mar 20, 2020

Sounds good to me

@alanz alanz self-assigned this Mar 20, 2020
@alanz alanz mentioned this issue Mar 20, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alanz alanz

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Preparing 0.21.0.0 release haskell/lsp
3 participants
@alanz @cocreature @lukel97