commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [JCS] Version 2 release
Date Tue, 04 Feb 2014 15:52:03 GMT
I think the biggest hurdle to releasing [JCS] 2.0 is finding a [Commons]
committer willing to put in the time to go over the component and act as
the release manager.

Gary


On Tue, Feb 4, 2014 at 10:46 AM, Mat Jaggard <matthew@jaggard.org.uk> wrote:

> I can't actually see any relevant issues in JIRA. They all seem to either
> relate to 1.3, be improvements rather than bugs or be an issue with Maven
> testing rather than the product.
>
> Are there any blocking issues or is it just testing time that's preventing
> 2.0 being released?
>
>
> On 4 February 2014 15:16, Gary Gregory <garydgregory@gmail.com> wrote:
>
> > I do not think we have a schedule for 2.0. If you want to help push it
> > out, I suggest you go through the Jira issues and see what you Figo
> should
> > be addressed.  You can post your ideas here. If you want to provide
> > patches, make sure you patch trunk and attach different files to Jira
> > issues.
> >
> > Gary
> >
> > -------- Original message --------
> > From: Mat Jaggard <apache@jaggard.org.uk>
> > Date:02/04/2014  06:16  (GMT-05:00)
> > To: Commons Users List <user@commons.apache.org>
> > Subject: [JCS] Version 2 release
> >
> > Hi,
> > Can you tell me when version 2.0 of JCS is likely to be released? What
> are
> > the blocking issues? Is there anything I can do to help?
> >
> > The main problem for me is using concurrent instead of the Java 5
> > equivalent.
> >
> > Many thanks,
> > Mat.
> >
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message