incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henning Schmiedehausen <>
Subject Re: [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
Date Wed, 17 Sep 2008 04:42:29 GMT

Here are my reasons:

- If incubator artifacts are distributed the same way as "regular"
artifacts, it removes one of the pain points for Incubator projects to
graduate. Personally, I feel this pain point is intended.

- It makes it too easy for other projects to depend on incubating
artifacts. This is something that we usually discourage, mainly because
every incubator podling has still a chance to fail, leaving other code
"hanging in the air".

- While we can not stop any repository or repository service to "pull"
incubator releases in and distribute them, we can control the active
distribution of incubator releases. "The central repository" is actually
not owned or even managed by the ASF, so we can not control what is in
there. Hence it is possible for this repo to contain GPL, ASF and other
licensed software, even commercial if they chose to do so. That is not
our call. So you can not compare this to the incubator releases. 

Remember, every incubating projects can push for graduation and should.
If this is a reason to graduate, even better.


On Wed, 2008-09-10 at 09:34 +0300, Jukka Zitting wrote:
> 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
> 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
> 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
>  <code><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:
> For additional commands, e-mail:

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

View raw message