> Due to known issues with NBI > There are other issues that currently affect delivering a macOS installer.
Would you mind summarizing the issues referred to here? If the issues are solved in the future, can we consider having official installers again? -- Eirik From: Neil C Smith <neilcsm...@apache.org> Reply-To: "dev@netbeans.apache.org" <dev@netbeans.apache.org> Date: Tuesday, March 25, 2025 at 11:40 AM To: dev <dev@netbeans.apache.org> Subject: [DISCUSS] Release artefacts for NetBeans 26 onwards Hi All, This follows some discussion threads here and on ASF Slack ... With branch for NetBeans 26 only 3 weeks away, we need to make a decision soon about what release artefacts we're going to include directly as part of the IDE's release process. Due to known issues with NBI we're currently not in a position to ship a Windows installer for NetBeans 26 from Apache. There are other issues that currently affect delivering a macOS installer. As we have to rethink all this anyway, it probably makes it a good time to look at all the things in the release process, what to keep, and how to make things more manageable in future. My suggestion would be to limit the NetBeans IDE artefacts voted on and directly delivered from Apache to - - Source zip - Binary zip - Maven artefacts This would mean dropping from the release vote and distribution - - All installers For installers we would point people at the community installers. These are currently migrating to a new home, of which hopefully there will be an announcement soon. There are also various other third-party packages not produced by PMC members. We could keep the ASF DEB and RPM packages with small overhead, mainly around testing, but it probably makes more sense to drop all at once. - VSNetBeans I know Martin is currently working on a release schedule plan for VSNetBeans to post here, so this might preempt that. A previous discussion covered coordinating branch dates rather than release dates. - NBMs and update centre This is all the NBMs published at https://downloads.apache.org/netbeans/netbeans/25/nbms/ as well as the update centre catalog XML on the NetBeans VM. These artefacts cause some overhead in the release process but get almost no usage (checked via https://infra-reports.apache.org ). An empty update centre XML could actually make it easier to ship updates on the very rare occasion we do so, and might even remove the need to use the VM at all for this. The other use case for the UC is for optional downloads of the platform for RCP apps using the legacy Ant build, but there are other options there. It would also be possible to publish all these later in case of unforeseen issues at time of release. Thoughts, or alternative solutions, welcomed. Let's try and get this resolved in the next week or so, though. Thanks and best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org<mailto:dev-unsubscr...@netbeans.apache.org> For additional commands, e-mail: dev-h...@netbeans.apache.org<mailto:dev-h...@netbeans.apache.org> For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
