On Wed, 27 Sept 2023 at 12:33, Eric Barboni <sk...@apache.org> wrote: > But I thing we should tesselate the repo for thoose native stuff and make > release that we later use on netbeans main repo. > Maven was a choice to simplify release process but may not be compatible > with macos.
I was in favour of a separate repo as well initially, but the workflow for the profile binaries means I've probably changed my mind. See the generate headers section of each build - https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml#L94 I assume we could check the headers into a separate repo? But I don't think we gain much by doing so, rather than adding a pre-build stage on the existing workflow to build a source bundle. > I cannot recall but I think some project use githubaction to make release > artefacts (sources + binaries) that are signed (this is per project/repo). So > maybe this could handle the issue. Yes, although signing is just for reproducible builds IIRC - trying to find something on this that isn't from the private members list. I assume this is the flow for mvnd releases? https://github.com/apache/maven-mvnd/blob/master/.github/workflows/release.yaml > Should we use nbpackage for macos/windows and make installer also "better" ? We already use nbpackage for macOS, and the Swift launcher is now built as part of that process. > Do we need to stick on release frame ? Or could we wait ? It would be better to hit the release if we can. 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
