commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Barrett" <JBarr...@sawyermedia.com>
Subject RE: [configuration] What do we need to do for a 1.0 release?
Date Tue, 04 Feb 2003 20:27:59 GMT
Are there any committers out there w/ some spare cycles?  There are 3 patches for configuration
listed on nagoya.

thanks,
+jeff

> -----Original Message-----
> From: robert burrell donkin
> [mailto:robertburrelldonkin@blueyonder.co.uk]
> Sent: Tuesday, February 04, 2003 10:44 AM
> To: Jakarta Commons Developers List
> Subject: Re: [configuration] What do we need to do for a 1.0 release?
> 
> 
> the first thing to do is to get promoted to the commons proper :)
> 
> the rules are here:
> 
> http://jakarta.apache.org/commons/charter.html
> 
> i'd say that the best place to start is with a good proposal.
> 
> - robert
> 
> On Tuesday, February 4, 2003, at 04:30 PM, Shapira, Yoav wrote:
> 
> > Hi,
> > I'd like to see a commons-configuration 1.0 release.  Even 
> an Alpha or a
> > Beta would be fine.  I'm willing to help to see this 
> release happen.  So
> > what do we need to do?
> >
> > As far as I can tell, there have been no code changes for a 
> couple of
> > weeks.  A couple of people have posted new code submissions, and I
> > entered them as enhancement requests into Bugzilla.
> >
> > So what are the next steps?  I've read the Decisions page, 
> including:
> >
> > Release Plan
> > A release plan is used to keep all volunteers aware of when 
> a release is
> > desired, who will be the release manager, when the 
> repository will be
> > frozen to create a release, and other assorted information to keep
> > volunteers from tripping over each other. Lazy majority decides each
> > issue in a release plan.
> >
> > And the Maven page on the release process at
> > 
> http://jakarta.apache.org/turbine/maven/development/release-pr
ocess.html
>
> But I'm uncertain as to the next step.  Do we need to create a
> configuration 1.0 release plan?  Appoint a release manager?  Or have the
> above been done already?
>
> Thanks ;)
>
> Yoav Shapira
> Millennium ChemInformatics
>
>
>
> ---------------------------------------------------------------------
> 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