Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 76572 invoked from network); 4 Apr 2009 19:57:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2009 19:57:53 -0000 Received: (qmail 97933 invoked by uid 500); 4 Apr 2009 19:57:52 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 97811 invoked by uid 500); 4 Apr 2009 19:57:52 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 97801 invoked by uid 99); 4 Apr 2009 19:57:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 19:57:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 74.125.46.157 as permitted sender) Received: from [74.125.46.157] (HELO yw-out-1718.google.com) (74.125.46.157) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 19:57:44 +0000 Received: by yw-out-1718.google.com with SMTP id 9so1057850ywk.60 for ; Sat, 04 Apr 2009 12:57:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=NicL//zpQimLu0aIBdp+awUo3affNkzWz3nDjn1mj8I=; b=cbWiGLskbSmO1gDKjSmkxdHf77sg+qYQrNEmkPZV/Hq6q1xTGAZ6rnc2lB4mRqtsvF FY5w/YsB6ZssZ7D+Ejzv++l/UG6FD3eGSA4glXo9V44qSmRjS1lcr0g6wColbUQX7x0F zmDkp3DJ4K8vpvXP5e1bnYQLDCm2BrpD5SU1Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=gnnhEVPVuoT0UnYuVePL6Sj9l2foYgJ2pbXJY5P+jJRpuFxy12uBqx35DyHu+MiHWT q8uFNJbShoZNx02O50oowcm4pfhViR6rS5C9Bzj8hoFhtoqW82d4ZI7ekDKSsQ3dyANL wG9yOfu0ljXSleBnWCs7d0yNFAgOvcmCvBOlM= MIME-Version: 1.0 Received: by 10.151.14.5 with SMTP id r5mr4967782ybi.48.1238875043069; Sat, 04 Apr 2009 12:57:23 -0700 (PDT) In-Reply-To: <49D7AC3E.3030403@gmail.com> References: <49D51906.5030201@free.fr> <49D7827B.10006@gmail.com> <25aac9fc0904041128q73e282b9y30069b76beb048d7@mail.gmail.com> <49D7AC3E.3030403@gmail.com> Date: Sat, 4 Apr 2009 20:57:23 +0100 Message-ID: <25aac9fc0904041257k61ed9151od5860a4ee6e7ace9@mail.gmail.com> Subject: Re: [math] releasing 2.0 ? From: sebb To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 04/04/2009, Phil Steitz wrote: > sebb wrote: > > > On 04/04/2009, Phil Steitz wrote: > > > > > > > Luc Maisonobe wrote: > > > > > > > > > > > > > Hello, > > > > > > > > A lot of work has been done on [math] last months. > > > > There are 9 issues still open in Jira with a target set to 2.0. Some > of > > > > them have already been almost processed, some could be finished soon, > > > > some could be postponed to 2.1. > > > > > > > > What do you think about preparing to release 2.0 in the next few weeks > ? > > > > I volunteer to do the realese work. For those of you who have taken > the > > > > burden of the remaining issues, do you intend to complete your work on > > > > them or do you prefer I assign them to me and close what I can do ? > > > > > > > > > > > > > > > > > > > I am +1 on pushing out 2.0. Here are some comments on the issues > assigned > > > to me. My geologic-time progress is unfortunately not likely to improve > > > over the next couple of weeks, so I am more than happy to let others > jump > > > in. > > > > > > > > > > Math is now dependent on Java 1.5 (according to the pom), but there > > seem to be quite a few missing @Override annotations. There are also > > some raw types. Of course these are not essential, but they would > > help. > > > > > I don't see either of these as essential and regarding the raw types, I > would prefer to limit the changes that are not backward-compatible. What do you mean by backward-compatible here? Do you mean compile-time or run-time? > > Also, what about thread-safety? There are a few Synchronized classes, > > which are presumably intended to be thread-safe. I'm not sure it's > > particularly necessary to have thread-safe Math classes, so long as > > the classes are not thread-hostile (there's at least one such; I'll > > file a JIRA shortly), but it would be useful to document which classes > > are which. > > > > > +1 to add general comments to user guide and web site. I'd like to see the individual class Javadoc include the details as well, but that could be added in due course as it will take a while. > > > > > > > MATH-207 - I am close to committing David's great patch with only minor > > > modifications and that should make us pretty much complete from code > > > perspective for the initial genetics release, modulo comments on the API > > > that may still come in. What will remain on this is user guide update. > > > Patches welcome! > > > MATH-114 - User guide update is all that remains. I should be able to > do > > > that. > > > MATH-136 - I would like to get this in, but there is some work > involved. > > > +0 to moving to 2.1 > > > MATH-169 - pushed to 2.1 > > > > > > I will look at MATH-197 if Brent does not catch this. > > > > > > MATH-194 is a can of worms that we should collectively open and clean > up. > > > > > > I suppose I should open an issue to track it, but the general problem > of > > > the multiple regression API being incomplete and the GLS class being > > > numerically suspect makes me think we may want to hold at least the GLS > > > class from the release. I will see what I can do. I am leaning toward > > > flattening the hierarchy, adding some basic stuff to the OLS class and > > > releasing just that class. I will start a separate thread on this issue > > > when I have a plan. > > > > > > > > > Thanks for volunteering for the RM duty! > > > > > > Phil > > > > > > > > > > > > > > > > > > > > > > Luc > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > To unsubscribe, e-mail: > > > > > > > > > > > dev-unsubscribe@commons.apache.org > > > > > > > > > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > dev-unsubscribe@commons.apache.org > > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > dev-unsubscribe@commons.apache.org > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org