+1 on the proviso that all incubator releases include the phrase
incubator/incubating in their version, artifact or group ID so that
its clear that its an incubator release.

Stopping incubating artifacts from being in the central repo is just
silly given they are already in a maven repo (its trivial for a
pom.xml to reference the incubating maven repo) so its not like it
stops folks including incubator releases transitively in any maven
project. Indeed few folks would even be aware whether the artifacts
came from the incubating repo or the public maven repo.

The only thing that really matters is that its clear - from the
groupID/artifactID/version tuple - that its an incubating release not
a full apache release. Stopping those artifacts from being in the
highly mirrored maven repos doesn't really help anyone IMHO.


2008/9/10 Jukka Zitting <[EMAIL PROTECTED]>:
> Hi,
>
> We've had a number of long discussions about the incubating projects
> using the central Maven repository to distribute their releases. The
> current policy is that incubating releases should not go to there. The
> related discussion threads have died with no consensus but the issue
> still exists and affects many podlings. I would like to finally
> resolve the issue one way or another by calling the Incubator PMC to
> vote on the matter.
>
> In INCUBATOR-82 I have prepared a patch (also attached below) that
> changes the policy document to explicitly _allow_ extra distribution
> channels like the central Maven repository for incubating releases.
> Note that the proposed patch allows any such channels instead of
> focusing just on the Maven repository. Also, any releases must still
> be approved, comply with the disclaimer and naming rules, and be
> primarily distributed through the official
> http://www.apache.org/dist/incubator/ channel.
>
> Please vote on accepting or rejecting this policy change! This
> majority vote is open for a week and only votes from the Incubator PMC
> members are binding.
>
> [ ] +1 Yes, allow extra release distribution channels like the central
> Maven repository
> [ ] -1 No, keep the current policy
>
> My vote is +1
>
> BR,
>
> Jukka Zitting
>
> Patch from https://issues.apache.org/jira/browse/INCUBATOR-82:
>
> Index: site-author/incubation/Incubation_Policy.xml
> ===================================================================
> --- site-author/incubation/Incubation_Policy.xml        (revision 692094)
> +++ site-author/incubation/Incubation_Policy.xml        (working copy)
> @@ -489,6 +489,8 @@
>         <p>
>  Releases for <em>podling</em> <strong>MUST</strong> be distributed through
>  <code>http://www.apache.org/dist/incubator/<em>podling</em></code>.
> +In addition, the Podling MAY choose to distribute approved releases through
> +other channels like the central Maven repository.
>         </p>
>       </section>
>       <section id="Use+of+Apache+Resources">
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to