commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lowe <mel...@gmail.com>
Subject Re: Steps prior to graduating from Sandbox
Date Wed, 03 Nov 2004 11:55:03 GMT
Eric

Have you got an email or something that doesn't involve the tedious
source forge sign up, for the dumpster guy?

I'm trying to get just a smtp session running (no other tests). This
is the root of the troubles I've been having. Anyway give me an email
and I'll get on the case.

Mark


On Wed, 3 Nov 2004 10:13:11 +0100, Eric Pugh <epugh@upstate.com> wrote:
> Maybe I should start another thread, but what do you think of the current
> state of [email].   We currently have a high level of unit testing, and it
> is building under Gump nicely.  We are working on resolving the Ant/Maven
> build issues.  I'd like to put out a feeler for graduating from sandbox
> before calling for a vote.  See what else we need.
> 
> My biggest concern is that I am the only active committer.  On the other
> hand, I don't see that the codebase in [email] can "mature" anymore then it
> has already!
> 
> Eric
> 
> 
> 
> > -----Original Message-----
> > From: robert burrell donkin [mailto:rdonkin@apache.org]
> > Sent: Tuesday, November 02, 2004 9:11 PM
> > To: Jakarta Commons Developers List
> > Subject: Re: Steps prior to graduating from Sandbox
> >
> >
> > in theory, all that's required is that a component satisfies the
> > requirements to be a commons component and passes a vote. (the sandbox
> > is free for people to play in but some sandbox projects should graduate
> > to somewhere other than the commons.)
> >
> > in practice, the question is what the consensus amongst commons
> > committers .
> >
> > willingness and preparedness for an initial release. this does not need
> > to be a 1.0, sometimes an API needs time to mature or there are major
> > features missing and in those cases a 0.x release might be more
> > appropriate. the aim should be to create an initial release immediately
> > after promotion.
> >
> > a healthy community of developers and users, as well as committers.
> >
> >
> >
> > - robert
> >
> > On 2 Nov 2004, at 12:11, Oliver Zeigermann wrote:
> >
> > > Unrelated, but do you know what would be the steps for a project to be
> > > graduated from the sandbox?
> > >
> > > Oliver
> > >
> > > On Tue, 2 Nov 2004 12:34:27 +0100, Eric Pugh
> > > <epugh@opensourceconnections.com> wrote:
> > >> Hi all,
> > >>
> > >> I started updating the Status.html doc.   I wanted to make sure we
> > >> have a
> > >> consensus on steps prior to proposing to graduate from the sandbox:
> > >>
> > >> 1) Remove commons-validator.
> > >> 2) Verify unit tests (dumbster) run on *NIX boxes
> > >> 3) Documentation enhancements?
> > >>
> > >> Does this look good?
> > >>
> > >> Eric
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > >> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message