Hi, On 7. 5. 2025, at 13:32, Neil C Smith <neilcsm...@apache.org> wrote:
Hi, On Wed, 7 May 2025 at 10:02, Martin Balin <mba...@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-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
