incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <>
Subject Re: [VOTE] Release Apache Ignite (Incubating) 1.0-RC3
Date Sun, 22 Mar 2015 10:54:07 GMT
Le 22/03/15 00:09, Marvin Humphrey a écrit :
> On Sat, Mar 21, 2015 at 2:16 AM, Dmitriy Setrakyan
> <> wrote:
> We wanted to have community to play with the RC3 release for a bit until we
> release the final 1.0 release in a week or two.
> Because "release candidate" and "RC" are specialized terms with
> precise meaning at Apache and because we make a strong legal
> distinction between "released" and "unreleased" code, this is
> extremely confusing.  Having something named "RC" which is also an
> official Apache release is... gah, it makes my brain hurt.


there is no such thing as a 'precise meaning' for any release at The
ASF. The project might decide to call it whatever they want (RC, GA,
Candidate, Milestone, or even Blueberry) if they want to.

This is totally unrelated to any legal aspect. Release is one thing, ie,
the very *process* of releasing some code, the name which is used to
expose the package being release is another thing.

It *might* be confusing though, I agree. What we currently do in many
project is to move along a thread of releases, like :

1.0-M1 -> 1.0-M2 ->... 1.0-Mx -> 1.0-RC1 -> 1.0-RC2 ->... 1.0-RCy -> 1.0

Mx are milestones
RCy are release candidate
1.0 is the stable version (often it's just RCy renamed)

I have also seen 1.0-GA in place of 1.0

> Please consider adopting different terminology in the future --
> "alpha", "beta", "golden master candidate / GM candidate", etc.

That's up to the project to decide what they want to adopt. This is a
good suggestion, but not commonly adopted.

One more thing : your build tool is most of the time a driver when it
comes to pick a scheme. You often want to be sure that a given revision
is seen as following all the others. Typically, if you are going to work
in a OSGi environment, the naming scheme you use for release is
extremelly important.

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

View raw message