On Wed, 9 Apr 2025 at 19:12, Jaroslav Tulach <jaroslav.tul...@gmail.com> wrote: > > 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. ... > - (preferably) bugfixes included in the main NetBeans repository (first)
This proposal seems somewhat in danger of becoming circular. The original plan was to decouple release processes due to workload sharing issues, and just to coordinate on initial branch points, not release hashes. Bugfixes that are only relevant to VSNetBeans would therefore hopefully be in master before plugin releases, but not necessarily on delivery, and therefore not in the Maven release artefacts. Syncing to a release hash of the IDE and platform means syncing to a hash that is never in master, and also syncing to a branch that might be missing those fixes from master. Depending on the ongoing frequency of VSNetBeans, which was intended to increase, there is at least the possibility of overlapping schedules, and history and module versions in the plugin then going backwards. Either we have a fully coordinated release process of the IDE, plugin and platform each quarter, which brings us back to sharing the workload properly. Or we have decoupled releases, and any use of the Maven artefacts in the VSNetBeans ecosystem is going to have some element of hit and hope! :-) 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
