You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Martin Balin <mb...@apache.org> on 2025/05/07 09:00:32 UTC

Re: [DISCUSS] VSNetBeans releases and repository changes

Hi Neil,

> On 28. 4. 2025, at 11:56, Neil C Smith <ne...@apache.org> wrote:
> 
> On Mon, 28 Apr 2025 at 10:04, Martin Balin <mb...@apache.org> wrote:
>> The proposal was there from April 9th in this form, I’m glad you are now reviewing it.
> 
> I reviewed it on the 10th!
> https://lists.apache.org/thread/o49173oy24775zo0spcflbo0xx3b5o4x
> 
>> OK, this is about releasing VSNetBeans using final commit from releasexyz branch right, when VSNetBeans is in its own repo. Right?
>> Whatever is released as main NetBeans release is then included in VSNetBeans built on top of it using that commit in submodule.
> ...
>> Decoupled releases was something we could agree on. I’ve read the thread from Jan about this and must say I didn’t understand by reading it what you mean by this? Can you explain it here on e.g. current May release of NetBeans 26 how this would look like, hypothetically? It will be better than me guessing...
> 
> Decoupled releases meant you branching at the same point as the IDE
> and platform (eg. I think branching from
> https://github.com/apache/netbeans/commit/27b43e77690d92eaf5d90e23d77b4626145c4d3f

I’ve created vsnetbeans_2600 branch from commit id you have recommended. Now we are running decoupled release process for VSNetBeans. Fixes for LSP are welcome on that branch.

> ) and running your own release process, which could have been done by
> now if you wanted.  It also meant decoupling from the issue tracking,
> milestones, metadata json, etc. used for the IDE and platform
> releases.

Martin
> 
> This is what you said you wanted to do in
> https://lists.apache.org/thread/kr2w5nfqp0yc9lbldpcmpp0j17szg7tv
> 
> It did not mean piggybacking on the IDE and platform release process,
> leaving the rest of us to stabilise and release those, unless the
> VSNetBeans team is also actively contributing to that work.
> 
> As I said on the 10th (emphasis added) - "Either we have a fully
> coordinated release process of the IDE, plugin and platform each
> quarter, which brings us back to **sharing the workload properly**.
> Or we have decoupled releases, ..."
> 
> I have always been in favour of a coordinated release process for IDE,
> platform and plugin, but not if it causes tensions with your desired
> release schedule, and not if the rest of this community is always
> being left to pick up the pieces!
> 
> Best wishes,
> 
> Neil
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: [DISCUSS] VSNetBeans releases and repository changes

Posted by Martin Balin <mb...@apache.org>.
Hello,

We have prepared 2 PRs which removes VSNetBeans code java/java.lsp.server/vscode and java/java.lsp.server/nbcode from NetBeans IDE main git repo as specified https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository+and+Updated+Releases
Changes in netbeans.git are in https://github.com/apache/netbeans/pull/8661 and updates to netbeans-jenkins-lib are in https://github.com/apache/netbeans-jenkins-lib/pull/129 these are now ready for review by anyone interested. Special thanks to Tomas Hurka who prepared these.
Once merged VSNetBeans will be decoupled from main NetBeans IDE as planned.

Best regards,
Martin Balin

On 2025/06/17 18:47:47 Martin Balin wrote:
> Hi,
> I’ve created a separate repo for VSNetBeans https://github.com/apache/netbeans-vscode
> It now contains sources from nbcode and vscode folders from netbeans.git java/java.lsp.server. Many thanks to Tomas Hurka for his Git expertise and thoroughness.
> 
> Netbeans-vscode is buildable as well as netbeans.
> Fixes for vscode and nbcode have to go to new repo.
> 
> Next steps (roughly):
> Build jobs for netbeans-vscode
> CI
> Source code artifact creation
> ...
> PR for main netbeans repo to remove what was moved as well as fix all builds to not build VSNetBeans there.
> 
> Regards,
> Martin
> 
> 
> > On 7. 5. 2025, at 13:32, Neil C Smith <ne...@apache.org> wrote:
> > 
> > Hi,
> > 
> > On Wed, 7 May 2025 at 10:02, Martin Balin <mb...@apache.org> wrote:
> >> I’ve created vsnetbeans_2600 branch from commit id you have recommended. Now we are running decoupled release process for VSNetBeans. Fixes for LSP are welcome on that branch.
> > 
> > I think that works for now, at least as an interim step for your
> > current release.  Before the following release you should think about
> > the separate release repo, CI and metabuild JSON.  Obviously, they're
> > my personal views, and other people, particularly thinking Eric, Jan
> > and Michael, might have additional release concerns to address in
> > this?  I think it is starting to align with previous discussions here
> > and on Slack?
> > 
> > At the moment we have no GitHub CI testing on vsnetbeans* branches.  I
> > presume you'll want some relevant testing on your release branches or
> > repo in future.  We just need to be careful to stay within the CI
> > resources we have.
> > 
> > At the moment we are triggering things on Jenkins with these branches
> > that are not necessary, although the usage here is small.  We should
> > still make sure we're only using what we need.  There's a whole load
> > of stuff there that should be rationalized anyway.
> > 
> > Best wishes,
> > 
> > Neil
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> > 
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > 
> > 
> > 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: [DISCUSS] VSNetBeans releases and repository changes

Posted by Martin Balin <mb...@apache.org>.
Hi,
I’ve created a separate repo for VSNetBeans https://github.com/apache/netbeans-vscode
It now contains sources from nbcode and vscode folders from netbeans.git java/java.lsp.server. Many thanks to Tomas Hurka for his Git expertise and thoroughness.

Netbeans-vscode is buildable as well as netbeans.
Fixes for vscode and nbcode have to go to new repo.

Next steps (roughly):
Build jobs for netbeans-vscode
CI
Source code artifact creation
...
PR for main netbeans repo to remove what was moved as well as fix all builds to not build VSNetBeans there.

Regards,
Martin


> On 7. 5. 2025, at 13:32, Neil C Smith <ne...@apache.org> wrote:
> 
> Hi,
> 
> On Wed, 7 May 2025 at 10:02, Martin Balin <mb...@apache.org> wrote:
>> I’ve created vsnetbeans_2600 branch from commit id you have recommended. Now we are running decoupled release process for VSNetBeans. Fixes for LSP are welcome on that branch.
> 
> I think that works for now, at least as an interim step for your
> current release.  Before the following release you should think about
> the separate release repo, CI and metabuild JSON.  Obviously, they're
> my personal views, and other people, particularly thinking Eric, Jan
> and Michael, might have additional release concerns to address in
> this?  I think it is starting to align with previous discussions here
> and on Slack?
> 
> At the moment we have no GitHub CI testing on vsnetbeans* branches.  I
> presume you'll want some relevant testing on your release branches or
> repo in future.  We just need to be careful to stay within the CI
> resources we have.
> 
> At the moment we are triggering things on Jenkins with these branches
> that are not necessary, although the usage here is small.  We should
> still make sure we're only using what we need.  There's a whole load
> of stuff there that should be rationalized anyway.
> 
> Best wishes,
> 
> Neil
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


Re: [DISCUSS] VSNetBeans releases and repository changes

Posted by Martin Balín <ma...@windowslive.com>.
Hi,

On 7. 5. 2025, at 13:32, Neil C Smith <ne...@apache.org> wrote:

Hi,

On Wed, 7 May 2025 at 10:02, Martin Balin <mb...@apache.org> wrote:
I’ve created vsnetbeans_2600 branch from commit id you have recommended. Now we are running decoupled release process for VSNetBeans. Fixes for LSP are welcome on that branch.

I think that works for now, at least as an interim step for your
current release.  Before the following release you should think about
the separate release repo, CI and metabuild JSON.
I will create new metabuild JSON file here https://github.com/apache/netbeans-jenkins-lib . I will ask for separate git repo via INFRA issue.
Obviously, they're
my personal views, and other people, particularly thinking Eric, Jan
and Michael, might have additional release concerns to address in
this?  I think it is starting to align with previous discussions here
and on Slack?

At the moment we have no GitHub CI testing on vsnetbeans* branches.  I
presume you'll want some relevant testing on your release branches or
repo in future.  We just need to be careful to stay within the CI
resources we have.
OK, thanks for bringing this up.


At the moment we are triggering things on Jenkins with these branches
that are not necessary, although the usage here is small.  We should
still make sure we're only using what we need.  There's a whole load
of stuff there that should be rationalized anyway.
If I understand you correctly then vsnetbeans_2600 branch will be built on Jenkins. Are these some other jobs than these https://ci-builds.apache.org/job/Netbeans/view/vscode/ ? This is what is used the most in my opinion.
Martin

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: [DISCUSS] VSNetBeans releases and repository changes

Posted by Neil C Smith <ne...@apache.org>.
Hi,

On Wed, 7 May 2025 at 10:02, Martin Balin <mb...@apache.org> wrote:
> I’ve created vsnetbeans_2600 branch from commit id you have recommended. Now we are running decoupled release process for VSNetBeans. Fixes for LSP are welcome on that branch.

I think that works for now, at least as an interim step for your
current release.  Before the following release you should think about
the separate release repo, CI and metabuild JSON.  Obviously, they're
my personal views, and other people, particularly thinking Eric, Jan
and Michael, might have additional release concerns to address in
this?  I think it is starting to align with previous discussions here
and on Slack?

At the moment we have no GitHub CI testing on vsnetbeans* branches.  I
presume you'll want some relevant testing on your release branches or
repo in future.  We just need to be careful to stay within the CI
resources we have.

At the moment we are triggering things on Jenkins with these branches
that are not necessary, although the usage here is small.  We should
still make sure we're only using what we need.  There's a whole load
of stuff there that should be rationalized anyway.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists