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

Migrate codebase to 2.13 #1974

Closed
ckipp01 opened this issue Aug 5, 2020 · 3 comments
Closed

Migrate codebase to 2.13 #1974

ckipp01 opened this issue Aug 5, 2020 · 3 comments
Labels
improvement Not a bug or a feature, but something general we can improve tech debt We should have addressed this yesterday

Comments

@ckipp01
Copy link
Member

ckipp01 commented Aug 5, 2020 •
edited
Loading

Creating this to track it since one doesn't exist yet. I think it'd be a good idea to do a migration from 2.12 to 2.13 in the Metals code base. One of the current blocks that I see is that bloop-launcher is not cross compiled to 2.13. There is a ticket for it here.
@ckipp01 ckipp01 added the improvement Not a bug or a feature, but something general we can improve label Aug 5, 2020
@ckipp01 ckipp01 added the tech debt We should have addressed this yesterday label Dec 29, 2021
@tgodzik
Copy link
Contributor

tgodzik commented Mar 11, 2022

Done in #3631 🎉

@tgodzik tgodzik closed this as completed Mar 11, 2022
@kpodsiad
Copy link
Member

Do we want Migrate codebase to 3 ticket? ;)

@tgodzik
Copy link
Contributor

tgodzik commented Mar 12, 2022

Let's maybe hold off for a bit still 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement Not a bug or a feature, but something general we can improve tech debt We should have addressed this yesterday
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tgodzik @ckipp01 @kpodsiad