incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <>
Subject Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts
Date Wed, 24 Jun 2015 17:07:10 GMT
Good point.
Furthermore, for users of those project, it might be more painful to get
binaries in an usual Apache place compared to a community / blessed

Le mercredi 24 juin 2015, Markus Weimer <> a écrit :

> > Personally I think the policy should be clarified such that nightly
> builds
> > MUST only live on ASF infrastructure (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.
> This is very tricky for projects outside the Java ecosystem. For .NET,
> NuGet is the established way to get packages, and the ASF doesn't
> provide a NuGet repository in the same way it does provide Maven
> repositories.
> NuGet is just one example, each of the major language ecosystems now
> offers at least one (binary) artifact and dependency management
> approach. Following through on the above would mean either an incredible
> workload for the ASF to support it all, the exclusion of whole languages
> from ASF projects or treating some as second class citizens because
> their nightly builds wouldn't be testable. Neither of those strike me as
> great results.
> Markus
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> <javascript:;>
> For additional commands, e-mail:
> <javascript:;>

Guillaume Laforge
Groovy Project Manager
Product Ninja & Advocate at Restlet <>

Social: @glaforge <> / Google+

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message