community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: What is the legal basis for enforcing release policies at ASF?
Date Thu, 20 Aug 2015 23:44:56 GMT
AFAIK a SNAPSHOT has not been voted on and is therefore not a formal
ASF release.

So for example this would cover CI builds that deploy jars to the ASF
Maven SNAPSHOT repo.


On 20 August 2015 at 23:33, Mike Kienenberger <mkienenb@gmail.com> wrote:
> On Thu, Aug 20, 2015 at 6:23 PM, Gavin McDonald <gavin@16degrees.com.au> wrote:
>> So what do we do about all the rc1|rc2|rcx ,alphas, betas and Milestone
>> ‘releases’ that are on our official mirrors right now?
>>
>> (Because they would have been voted on as a ‘’release’’ for the projects
to
>> put them there in the first place)
>
> "Release" means different things in different contexts.  An ASF
> release is a product that a PMC has vetted to meet ASF release
> standards (builds from source, APL2 licensed) and has made available
> to end-users in our download services.  This use of "release" deals
> with legal and "can-be-modified" promises made to the end-user.
>
> Various ASF projects also use "release" to mean something different --
> a community-approved product that has a certain API and typically has
> no known issues.  This use of "release" generally deals with technical
> aspects of the project, such as stability and reliability.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Mime
View raw message