On Mon, 1 Feb 2021 at 10:27, Lars Bruun-Hansen <[email protected]> wrote: > Yep. I was considering that the right place for such internal > artifacts might be ASF's Maven Repo. The problem I see with that one > is that it is meant for _released_ artifacts meaning official ASF > releases. They need to go through the voting process. This is not the > case for these particular artifacts, they are in effect interim, and I > don't think the community need more artifacts that we need to vote > on?.
Firstly, let's separate out sources and binary artefacts here - sources *require* votes, although we do generally vote on binary artefacts too. IMO, if a pre-built binary is being consumed by an end-user building our sources or a platform developer building their project, then we should be treating it as a released artefact, and it might be a lot less complicated if we did. I would note that the Windows launchers are built as part of the release process on Jenkins. There may be pros and cons to that in terms of being in sync with people building locally? Having all the native binaries released officially via ASF Maven repos (or dist.a.o) might actually be better, and people can still check out their sources and build locally if they want. 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
