incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <>
Subject Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts
Date Wed, 24 Jun 2015 20:14:36 GMT
On Wed, Jun 24, 2015 at 3:22 PM, Emmanuel Lécharny <> wrote:
> Le 24/06/15 09:19, Rob Vesse a écrit :
>> Personally I think the policy should be clarified such that nightly
>> builds MUST only live on ASF infrastructure
> Non sense. Nightly built can stay wherever is suitable. It's not The ASF
> business anyway, The ASF does not endorse nighly build or non-release
> packages.
>> (whether that be the Nexus SNAPSHOTs repo, committer web space etc).
>> As soon as you start putting them on external services like DockerHub
>> then they are potentially widely visible to the general public.
> Not a problem, as soon as you don't advertize them. People are grown up
> adults that know what to do with such builds, would they found them
> somwhere which is not advertized as an Apache official release.
>> Going back to the example of libraries published as Maven artifacts
>> for those projects already publishing SNAPSHOTs these only get
>> published to the Apache Nexus server ( and are
>> not synced to Maven central.
> So ? SNAPSHOTs are visible, anyone can download them, and they are not
> endorsed by apache. They are just stored there because it's convenient,
> not because it's official or whatever makes an ASF release.

The reasoning is that artifacts on repository.a.o are hard to find,
hard to come across. It's not in Maven Central.
We aren't hiding them, but for someone to consume them would require
them taking explicit action that short of them being in the project
community they won't know about.
We don't publish those artifacts to central, because people would
easily find and consume them.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message