On Fri, 5 Feb 2021 at 14:38, Eric Bresie <[email protected]> wrote: > On Mon, Feb 1, 2021 at 5:11 AM Neil C Smith <[email protected]> wrote: > > 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, ... > > > > 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. ... > Taking a step back (and expanding a little), I'm trying to understand the > use cases, scope and usage of the artifacts > > Assume there are: > (1) netbeans sources code for building
Perhaps a bigger step back?! :-) At least in terms of what I'm getting at. Apache releases sources. We only vote on one source bundle for each release from the NetBeans repo. Even other source bundles, such as platform sources, are really treated as a build artefact. Convenience artefacts (or binaries, but as said some aren't binaries) should be verifiably built from that voted on source bundle. As much as possible that's part of the checking process and voting on them. Now IMO, there's something of a chicken and egg problem with the source bundle linking to binary artefacts of that source bundle. So unless everyone who builds the NetBeans sources has to build all the native binaries on each platform for themselves, there's something of a fudge going on. Not one that's that concerning ... assuming we ensure there's no way the released sources and referred to binaries can ever get out of sync! However, if we treat them as properly released artefacts, then there's no fudge. It reflects the fact that they're not really interim if we're providing them as convenience binaries for people building various other sources. And it may also solve a bunch of issues for ourselves in terms of considering how to manage them and simplify our build processes in future. 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
