Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (nike.apache.org: domain of brianf@reply.infinity.nu
 designates 205.210.42.66 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: releases using incubator artifacts
Date: Mon, 12 Nov 2007 07:15:56 -0500
Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E25EAF9@intrepid.infinity.nu>
In-Reply-To: <073001c8251c$856b4190$0920a8c0@isabelteam.be>
Thread-Topic: releases using incubator artifacts
Thread-Index: AcglF81dtaAQNgWqSwys/EV8tX9XvgAAFR8AAANdJ6A=
References: <c84a50780711120235i38cbee86jf01c7f33ddcdff9b@mail.gmail.com>
 <073001c8251c$856b4190$0920a8c0@isabelteam.be>
From: "Brian E. Fox" <brianf@reply.infinity.nu>
To: <repository@apache.org>

I agree that releases shouldn't use incubator artifacts, but I can also
see that if this is the case, the incubator projects will never find
users and thus would never get out of the incubator. The only thing that
makes sense then is to publish them to central. If they are official
releases signed off by the incubator PMC, then what's the harm? The
current method of not publishing them AND allowing them to be used is
troublesome.

-----Original Message-----
From: Gilles Scokart [mailto:gscokart@gmail.com]=20
Sent: Monday, November 12, 2007 12:10 PM
To: repository@apache.org
Subject: RE: releases using incubator artifacts

There shouldn't have a release of an apache product depending on
incubator artefact.  Right, but the people outside
apache should be free to use it.  The central repository not only
contains official apache release.  Moreover,
incubating project are making release (well, incubator project is doing
it), distributed under Apache license. =20

So why not place them in central, provided that there is a clear
disclaimer in the POM that this is an incubating
release.


By the way, according to [1], "Every incubator release is also an Apache
release".
Note also, that according to the same document,=20
"It is best to use the groupId and artifactId that will be used upon
graduation. The version should include incubating
(or incubator) to ensure that the artifacts created comply with
Incubator release policy."


[1] http://incubator.apache.org/guides/releasemanagement.html

Gilles

> -----Original Message-----
> From: Steve Loughran [mailto:steve.loughran@gmail.com]
> Sent: lundi 12 novembre 2007 11:35
> To: repository@apache.org
> Subject: Re: releases using incubator artifacts
>=20
> On Nov 12, 2007 10:15 AM, Brian E. Fox <brianf@reply.infinity.nu>
wrote:
> >
>=20
> > It seems to me that we either need to allow the incubator artifacts
into
> > central, or we don't allow artifacts depending on incubator
artifacts into
> > central, it shouldn't be both.
>=20
> shouldnt be a release depending on incubator stuff...files in
> incubator are not official apache releases, are they?