Hi, We have consensus to separate VSNetBeans code as specified in proposal https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository+and+Updated+Releases to its own repository. As the 1st step I will start with getting new Git repo under GitHub.com/Apache. Upcoming release will be done in “hybrid” mode. I will release VSNetBeans 26.0.0 from netbeans repo “release260” branch after VOTE on NetBeans 26.0 is complete. It will be release of complimentary artifact done from the same source as main release. I’m not sure how quickly we will get netbeans-vscode repo. I assume it might take some time. If nobody objects then I’m going to work on afore mentioned plan
Martin > On 10. 4. 2025, at 15:11, Martin Balín <mart...@windowslive.com> wrote: > > > >> On 9. 4. 2025, at 20:12, Jaroslav Tulach <jaroslav.tul...@gmail.com> wrote: >> >> 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” > Same as in release branch or in tag from master used for by submodule of > NetBeans main git repo > >> - when you change any API? > We don’t plan to change API in incompatible way, I remember from Sun > Microsystems days this is almost impossible, right Jaroslav? ;-) > The situation now will not be different too much for Enso than it was before. > Releases of VSNetBeans done for main IDE release and some interim releases > following JDK schedule. > Martin >> >> 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
