On Fri, 2 Jul 2021 at 17:03, Eric Barboni <[email protected]> wrote: > > > Is a beta needed for 12.5 ? > > Well, there were two reasons we ended up with a beta for 12.4. > Primarily it was to allow a VSCode plugin update.
Tomorrow I'd like to branch VSNetBeans 12.4.301 preview release that we had planed to expose on VSCode Marketplace for weeks: https://lists.apache.org/thread.html/rd3b6350f7791467ba36a3015a70e497122e943a330194100082f1e3e%40%3Cdev.netbeans.apache.org%3E The last PR I am waiting for is https://github.com/apache/netbeans/pull/3045 I create a branch called vsnetbeans124-3 and then I'd like to execute the parametrized build of https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/ job to create the `.vsix` binary. However, to make sure the changeset is recognized via the downloaded meta/netbeansrelease.json file, I need to create a pull request for the https://github.com/apache/netbeans-jenkins-lib and record the changeset there, right? I tried to find some info about the process at https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule and related pages, but I found nothing. So I am just guessing... With meta/netbeansrelease.json file in, I can run the https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/ job and get the properly labeled binary. However we'll have to vote over sources as well. They are usually produced by https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/ job (according to emails from release managers). I hope I'll be able to reuse it as well, but only tomorrow experiments show whether that is just my naive dream or something close to a real plan. If that fails, I prepare the sources locally. I rely on guidance of our experienced release managers. In the here-in discussion, in the PR, etc. Thank you in advance for your help. -jt
