incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <>
Subject Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts
Date Wed, 24 Jun 2015 02:48:42 GMT
On Tue, Jun 23, 2015 at 3:20 PM, Ross Gardler (MS OPEN TECH)
<> wrote:
> There is nothing preventing "clearly identifiable non-release artifacts
> available to the general public". Many projects make automated nightly builds available
for example.

This! Honestly this has always been my personal interpretation of the policy
(although now that I'm re-reading it I see how it could be interpreted in a
radically different way).

IOW, I've been mentoring a lot of poddlings and advising them that as
long as they go out of their way to label 'nightly' artifacts as NON RELEASE,
DON'T TRY IT AT HOME, DANGER!!! it is ok to make them available to
"general public" (*). I have always though that, for example, -SNAPSHOT version
designation is enough to communicate that  type of intent. Same as
SNAPSHOT/NONRELEASE tag on Docker image, etc.

>From what you're telling me it sounds like this should be acceptable to ASF
(I know you're just voicing your viewpoint, not the official ASF). That still
leaves the question of updating the policy which I'd love to collaborate
with somebody to update -- but I don't think I can sign up for that job all
by myself.


(*) an come on, do you really think that *general* public consumes something
like apache common? These are our fellow developers -- they really don't
have to be told what -SNAPSHOT designation means.

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

View raw message