The proposed voting order seems ok to me. 

Please note that I didn't say that the 2.0 final release should be done
as an incubator project; I was just wondering what's customary. 
Notwithstanding my previous post, I would love to see ivy graduated as
an ant subproject. I use it (almost) every day...

Erik-Berndt

-----Oorspronkelijk bericht-----
Van: Gilles Scokart [mailto:[EMAIL PROTECTED] 
Verzonden: maandag 17 september 2007 11:11
Aan: [email protected]
Onderwerp: RE: What about Graduation?




> -----Original Message-----
> From: Xavier Hanin [mailto:[EMAIL PROTECTED]
> Sent: lundi 17 septembre 2007 10:41
> To: [email protected]
> Subject: Re: What about Graduation?
> 
> On 9/17/07, Scheper, Erik-Berndt <[EMAIL PROTECTED]> 
> wrote:
> >
> > Hi,
> >
> > Before starting a vote thread, wouldn't it be better to clear some 
> > outstanding issues: -Is it still intended to graduate as an ant 
> > subproject? (I seem to remember that I read this some time ago)
> 
> 
> We agreed on graduating as an Ant subproject a few months ago:
> http://www.nabble.com/Destination-upon-graduation-%28was-Re%3A-Steps-
> toward-graduation%29-tf3882862.html#a11004970
> 

You are right, we were all agreeing on that.  But that should be
formalized with a vote.  Isn't it?

Also, a vote the ant-dev mailing list will be required.

But I'm not sure in which order we should make those votes...  I propose

1. Vote here on destination after graduation
2. Ask for a vote on the ant-dev mailing list (if vote 1. result is as
expected)
3. Fire the vote here to decide if we are ready to graduate (if the
result of vote 2. is as expected, and depending on the outcomes of this
discussion) 4. If ok, ask the vote on the incubator list.



> 
> -Wouldn't it be better to wait until an incubating release (better 
> than
> > alpha-2) is complete? The beta-1 release has been delayed for some 
> > time now
> 
> 
> I personnally don't think so. Graduation is not about code quality or 
> release quality. We have demonstrated we are able to make releases. 
> Being late on a release is a problem we frequently encounter in an 
> open source project. Committers sometime have less time than expected 
> to work on a release, but I don't think it's too much a problem, the 
> community is still there, answering questions, and developing the 
> upcoming version. And I would really prefer to make the 2.0 final 
> version as a graduated project.
> 

I have the same understanding.



Gilles



Disclaimer:
This message contains information that may be privileged or confidential and is 
the property of Sogeti Nederland B.V. or its Group members. It is intended only 
for the person to whom it is addressed. If you are not the intended recipient, 
you are not authorized to read, print, retain, copy, disseminate, distribute, 
or use this message or any part thereof. If you receive this message in error, 
please notify the sender immediately and delete all copies of this message.

Reply via email to