Right, those packages should be kept in sync. Please publish in the inverse order of dependencies and update the dependencies accordingly (e.g. to sprotty-protocol). The other sprotty-vscode and sprotty-eclipse repos currently have independent release cycles.
Yes, a release record should be created, but without release review (I think the last review was for 0.10.0, less than a year ago).
Thank you! Miro
Hi Miro,
yes I can take over this release. I think naming it 0.12.0 definitely makes sense. As you already said there are still a couple of issues we need to address before we are leaving the incubation phase with 1.0.0.
Just to make sure, which packages are typically part of a sprotty release? - The packages of the main repo - sprotty Hi Philip,
yes, no objections from my side. Shall we name this 0.12.0? We also want to publish 1.0.0 at some point (I hope later this year), but I think we should work on a graduation review before that.
Philip and Tobias, could you take over this release? - Create a v0.12.0 milestone and assign all fixed issues and merged PRs to it (maybe change milestone from v1.0.0 to v0.12.0)
- Update CHANGELOG.md in all packages
- Publish to npm (Tobias and I have access)
Thanks
-- Dr. Miro Spönemann General Manager / Software Architect TypeFox GmbH Am Germaniahafen 1, 24143 Kiel https://www.typefox.ioTel.: +49 151 42679459 Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 Geschäftsführer: Daniel Dietrich, Dr. Miro Spönemann
Hello Sprotty team,
For an upcoming GLSP release, we would need a Sprotty release to ensure that GLSP only depends on released versions. Ideally, this release would contain master and the already approved PR #293 [1]. After checking with @gabrieldulca, he said he'll be able to rebase in the next 2 days. Would it be ok with you to do a release at the end of the month?
Thanks a lot in advance and best wishes,
Philip
_______________________________________________ sprotty-dev mailing list sprotty-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sprotty-dev
_______________________________________________
sprotty-dev mailing list
sprotty-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sprotty-dev
-- Tobias Ortmayr
Senior Software Engineer EclipseSource Austria
EclipseSource Services GmbH Schwindgasse 20 / 2-3 1040 Wien
General Manager: Dr. Philip Langer Registered Office: Schwindgasse 20 / 2-3, 1040 Wien; Handelsgericht Wien, FN 421413a
_______________________________________________ sprotty-dev mailing list sprotty-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sprotty-dev
|