Thank you for your reply Eric!
I think you need to create the new "vs*branch entry in the json. I'm not > sure of the Regexp detection and I hope it's not locked to master or > release* . > Just for simplicity do PR if you want but just direct commit is fine too. > It's only working if pushed. > +1 > We may also add to the build itself to produce vsix Yes, that would be excellent! We want to release new version of .vsix everytime NetBeans version is released! > if branches start with vs. > No need to check for that. Whenever there is new version of NetBeans, like NetBeans 12.5 - we want to release `apache-netbeans-12.5.0.vsix` - e.g. we want to release from every release branch. Sometimes we want to release more frequently (like now with 12.4.301), but hopefully such extra releases will become more and more rare. -jt > > -----Message d'origine----- > De : Jaroslav Tulach <[email protected]> > Envoyé : lundi 12 juillet 2021 20:55 > À : dev <[email protected]> > Objet : Branching VSNetBeans 12.4.301 tomorrow was: Beta for Apache > NetBeans 12.5 > > 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 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
