-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Endgame Plan for release 1.60 #15216
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
Comments
Not sure how others feel about it, but personally, I would hold up the release for #15145. It's super-annyoing! |
Moved out #15205. No emergency to merge this PR onto the next release, and there are higher prio items on the list. |
@rschnekenbu 👍 on this one: merging a 30 file change when we're trying to stabilize is not a winner move ;-) |
As announced in discussion #15381, release 1.60 was done. Closing this endgame task. |
@rschnekenbu Can you move out the non closed items? |
@JonasHelming, I can move them to a new ticket for release plan 1.61. WDYT? |
Yes, or IDE epic, depending on the plan |
I missed the post-release action, so I reopened the task. |
Aftermath is done... |
Endgame issue for the 1.60 release.
We made a change (migration from PhosphorJS to Lumino) that will be release with Theia 1.60. This change may have some impacts on the tool (see #14320 ). A beta version would allow early testing for developers and early testers.
Pre-release 1.60 (03/20/2025?) (available)
Blocking:
Nice to have:
Release 1.60 (04/03/2025)
Blocking:
After Release
Nice to have
The text was updated successfully, but these errors were encountered: