Dne středa 9. dubna 2025 14:55:24 CEST, Martin Balín napsal(a): > Proposal was updated to address Jaroslav concerns > > https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository+a > nd+Updated+Releases
Thanks. I see: > After release of NetBeans IDE (Swing app) when VOTE is closed and final commit in release branch is known. Then submodule with main NetBeans repository will be updated to checkout this commit. This makes the VSCode extension "eventually consistent" with NetBeans IDE Maven artifacts under assumption: - no incompatible changes in the "submodule" - as little as possible of API changes in the "submodule" - bugfixes (without changing API) allowed, but ... - (preferably) bugfixes included in the main NetBeans repository (first) Question I haven't heard answer to: - what will be the versioning on modules in the "submodule" - when you change any API? But yeah, you can try this. It can work for Enso, if there is goodwill on all sides. -jt --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists