commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@multitask.com.au
Subject Re: [jelly] Is the CVS committer gone?
Date Thu, 28 Aug 2003 05:55:57 GMT
Bill, a list of bugs is one thing, but what we really need to do is 
schedule them into a release.

See 
http://jira.codehaus.org/secure/BrowseProject.jspa?id=10012&report=roadmap 
for what I started on.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/


Bill Keese <billk@tech.beacon-it.co.jp> wrote on 28/08/2003 03:32:13 PM:

> Hmm, forgot to mention in my original post, but all patches should be 
> entered into the JIRA bug database  For example here's are the current 
> jelly bugs:
> 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&query=jelly&summary=true&description=true
> 
> 
> Bill
> 
> 
> dion@multitask.com.au wrote:
> 
> >Bill, help us by pointing out your patches until we do apply them :-)
> >--
> >dIon Gillard, Multitask Consulting
> >Blog:      http://blogs.codehaus.org/people/dion/
> >
> >
> >Bill Keese <billk@tech.beacon-it.co.jp> wrote on 28/08/2003 11:46:58 
AM:
> >
> > 
> >
> >>Most of the developers for Jelly aren't actively involved with it 
> >>anymore (not even applying patches), but recently Peter Royal became a 

> >>new committer and has been trying to clean it up some.  But there are 
a 
> >>lot of problems with Jelly and only one active committer, so it may 
take 
> >> 
> >>
> >
> > 
> >
> >>a while for your patches to get posted.  I am waiting for my patches 
to 
> >>be posted also.
> >>
> >>Bill
> >>
> >>Sean W. Ferguson wrote:
> >>
> >> 
> >>
> >>>I've posted a couple of updates to JIRA for Jelly and haven't had any 

> >>>response or anything to them.  Is the person responsible for posting 
> >>>updates away, or am I just being ignored since my updates aren't that 

> >>>important? :)
> >>>
> >>>Sean
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message