> > On 31. 1. 2025, at 17:31, Neil C Smith <neilcsm...@apache.org> wrote: > > Personally I'd also like to see a hard limit on the number of > > VSNetBeans releases between IDE releases in case of release delays in > > future. > VSNetBeans releases in between IDE releases: ... > And we also need to decide if VSNetBeans will be released as part of main > NetBeans IDE release. Or it will be done separately by me (likely from same > code). Both works for me.
OK, let's deal with the elephant in the room here first! No NetBeans IDE, no VSNetBeans. No NetBeans IDE releases, no VSNetBeans releases. If these projects are to remain developing and coexisting within a single repository, then *everyone* working on that repository has to take some shared responsibility for ensuring the delivery of *all* its release components. The IDE, the VSCode plugin, and also the full range of platform artefacts. That includes issue management, PR reviews and rc testing across the board. When you were invited on to the release team, the intention was to share the release aspects of this workload out across the components. As of yet, neither you nor anyone else from the VSCode side has led on a full release or release candidate. Half of VSNetBeans' releases have been via that process. That situation is just not sustainable. When I took a break from the release team, I was hopeful that everything would not be left to one person, Eric. We had discussions around that, but from my perspective it doesn't feel like it's resolved much. Also, changes in the repository for VSNetBeans have a knock on effect on the IDE and platform. The first vote for NetBeans 24 had to be pulled because changes added solely (afaik) for the plugin caused a serious issue. That was not a one-off. Pulling a vote delays the full release by at least a week, and causes hours of extra work for the release manager. One consequence of not sharing this workload more fairly is going to be that people start vetoing changes in the IDE's code that bring no discernible benefit to the IDE or platform. Can I also be clear that personally I want this to work, and I want the development to continue within the single overarching repository. But unless we can realistically address the release capacity issue, it will fall apart, and that's no use to anyone! > Not sure I understand what you mean here Neil. Is it moving branching dates > for VSNetBeans and NetBeans release earlier to same date? Branch both on e.g. > Jan 11th when these releases could be overlapping like in a case of > VSNetBeans 24.9.9 and NetBeans 25? Or move branching dates far apart? So in > the case of VSNetBeans 24.9.9 will branch around Jan 6th to make sure it > releases before Jan 15th when NetBeans 25 release branch would be created? IMO they should share branch points as that makes it much easier on both sides to understand what is included, and to stabilise towards the point of branch. I also think, given another conversation today, that reconsidering the IDE branch and release points in relation to JDK releases would be a good thing anyway. > What will be the purpose of such branching repo? Like fork of whole NetBeans > code base on which VSNetBeans release will happen? Is this what you mean? I think Michael put this quite well earlier in this thread? 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
