Neil, The proposal was there from April 9th in this form, I’m glad you are now reviewing it.
> On 25. 4. 2025, at 12:16, Neil C Smith <neilcsm...@apache.org> wrote: > > On Fri, 25 Apr 2025 at 07:24, Martin Balin <mba...@apache.org> wrote: >> Today I consider it closed and proposal for VSNetBeans own repo approved >> https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository+and+Updated+Releases >> I will start working on getting the repository under Apache umbrella on >> GitHub. > > If you mean approval based on consensus, then that possibly exists if > you remove the last bullet point - > > "After release of NetBeans IDE (Swing app) when VOTE is closed and > final commit in release branch is known. Then submodule with main > NetBeans repository will be updated to checkout this commit." > > So, you can push for a vote with that in (which I'll -1) or we can revise > this. 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. > > I do not see how this is meant to work for you anyway. > > Take the scheduled CPU in October - https://www.java.com/releases/ > > We are scheduled to freeze and branch for the IDE and platform on > October 15th, which should release November 15th-30th. The CPU > release is October 21st. > > Do you intend to take a branch from master at the same time as the > main release and release that almost straight away? Or will you > branch later, in which case all module versions will have been > incremented and changes for the following release may already be in > master? > > There is no guarantee that features, and even new APIs, don't get > removed during stabilization on delivery. > > If VSNetBeans is not a release deliverable of the main release, then > fixes that only target it will not be going into delivery. > > All in all, any release based on the release hash of the IDE and > platform is likely to lead to a situation where your release goes > backwards! > > If you want to run a decoupled release process, then can we do that? > Let's agree coordinated branch points like we discussed before, and > then let the two processes run independently without needing to > consider each other. 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... Martin > > And yes, a consequence of that could be minor inconsistencies between > the plugin and the Maven release, but I see no way around that if you > want to decouple! > > 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 > > > --------------------------------------------------------------------- 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
