+1.

A release is a release is a release. If we are concerned about projects
staying in the incubator, then let's ban them from releasing anymore.
Or, say, only max five releases during incubation. But once a release is
done under the ASL, there's not really much we can do to stop its onward
distribution.

Regards, Upayavira

On Tue, 2008-09-23 at 09:00 -0400, Jim Jagielski wrote:
> -1 (Binding)
> 
> On Sep 22, 2008, at 6:41 PM, Paul Querna wrote:
> 
> > -1, (Binding).
> >
> > (For the reasons explained by Craig and Justin in this Thread)
> >
> > Thanks,
> >
> > Paul
> >
> > Craig L Russell wrote:
> >> -1
> >> I believe that allowing incubating releases to be treated as full  
> >> Apache releases diminishes the Apache brand and makes incubation  
> >> disclaimers moot.
> >> With Maven, it is too easy to depend on a release with transitive  
> >> dependencies on incubating releases without even knowing it. When  
> >> the incubating release subsequently is abandoned, blame will be  
> >> cast widely, including Apache itself.
> >> Considering that dependencies on incubating releases can be  
> >> resolved by explicitly adding an incubating Maven repository into  
> >> your settings, I don't think that wide, mirrored, distribution is  
> >> warranted.
> >> Craig
> >> On Sep 9, 2008, at 11:34 PM, 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
> >>> 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]
> >>>
> >> Craig L Russell
> >> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> >> 408 276-5638 mailto:[EMAIL PROTECTED]
> >> P.S. A good JDO? O, Gasp!
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

Reply via email to