You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stephen Colebourne <sc...@btopenworld.com> on 2002/12/17 10:07:38 UTC

[email] Tasks before promotion

Henri wrote:
> i)   Does it have a suitable level of javadoc. Not enough for an actual
>      release, but the bare minimum.
> ii)  Does it have maturity. That is, has it spent some time in the sandbox
>      while the developers use it, modified versions or extended versions
>      in other projects.
> iii) Does the project contain enough in the way of Unit Tests to show that
>      the developers are serious about testing.
> iv)  Is there a community, or is it a single developer. Does it have link
>      to another project which will show a scope for its community growth.
> v)   Does it have a webpage yet?

[email] needs unit tests

[email] needs a webpage

[email] needs evidence of more than one commons committer willing to apply
patches/support.

[email] needs to change its package name or component name (the package is
mail not email)

I agree that its time to get this one promoted.

Stephen


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: [email] Tasks before promotion

Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
surely, the most important criteria has been missed:

email needs a PROPOSAL document.

- robert

On Tuesday, December 17, 2002, at 09:07 AM, Stephen Colebourne wrote:

> Henri wrote:
>> i)   Does it have a suitable level of javadoc. Not enough for an actual
>>      release, but the bare minimum.
>> ii)  Does it have maturity. That is, has it spent some time in the 
>> sandbox
>>      while the developers use it, modified versions or extended versions
>>      in other projects.
>> iii) Does the project contain enough in the way of Unit Tests to show 
>> that
>>      the developers are serious about testing.
>> iv)  Is there a community, or is it a single developer. Does it have link
>>      to another project which will show a scope for its community growth.
>> v)   Does it have a webpage yet?
>
> [email] needs unit tests
>
> [email] needs a webpage
>
> [email] needs evidence of more than one commons committer willing to apply
> patches/support.
>
> [email] needs to change its package name or component name (the package is
> mail not email)
>
> I agree that its time to get this one promoted.
>
> Stephen
>
>
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.
> org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.
> org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: [email] Tasks before promotion

Posted by di...@multitask.com.au.
"Stephen Colebourne" <sc...@btopenworld.com> wrote on 17/12/2002 
08:07:38 PM:

> Henri wrote:
> > i)   Does it have a suitable level of javadoc. Not enough for an 
actual
> >      release, but the bare minimum.
> > ii)  Does it have maturity. That is, has it spent some time in the 
sandbox
> >      while the developers use it, modified versions or extended 
versions
> >      in other projects.
> > iii) Does the project contain enough in the way of Unit Tests to show 
that
> >      the developers are serious about testing.
> > iv)  Is there a community, or is it a single developer. Does it have 
link
> >      to another project which will show a scope for its community 
growth.
> > v)   Does it have a webpage yet?
> 
> [email] needs unit tests
+1.

> [email] needs a webpage
It already has one. See http://jakarta.apache.org/commons/sandbox/email/

> [email] needs evidence of more than one commons committer willing to 
apply
> patches/support.
So far we've had Jon, Sam and myself jumping in. Is that not more than 
one?

> [email] needs to change its package name or component name (the package 
is
> mail not email)
+1.

> I agree that its time to get this one promoted.
This will require a promotion of util, wont it? If email is to go to 
Commons Proper, and it depends on util and an unreleased lang, don't we 
need to get all three in a ready state?

--
dIon Gillard, Multitask Consulting
Blog:      http://www.freeroller.net/page/dion/Weblog
Work:      http://www.multitask.com.au


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>