On Sun, 31 Jan 2021 at 19:18, Lars Bruun-Hansen <[email protected]> wrote: > I had the exact same idea for example in relation to Apache NetBeans > native artifacts (launcher, nbi libs, nbi launcher, profiler libs) > because the https://netbeans.osuosl.org/binaries/ is really meant to > be a site for truly external binaries, i.e. those that are *outside* > of the Apache NetBeans project. So using something more internal to > the build pipeline would be preferable.
Well, if they're our "internal" artefacts then an internal release process would certainly be preferable. If we can consider certain chicken-and-egg issues here (ie. binaries required at IDE build time), then a separate source and binary release process for these and distribution via standard ASF channels might be the right way to approach this? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
