Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 3761 invoked from network); 5 Apr 2009 09:36:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Apr 2009 09:36:29 -0000 Received: (qmail 62589 invoked by uid 500); 5 Apr 2009 09:36:29 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 62467 invoked by uid 500); 5 Apr 2009 09:36:28 -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 62457 invoked by uid 99); 5 Apr 2009 09:36:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2009 09:36:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 72.14.220.156 as permitted sender) Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2009 09:36:21 +0000 Received: by fg-out-1718.google.com with SMTP id l27so620996fgb.1 for ; Sun, 05 Apr 2009 02:35:59 -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=k+5FrWr6pJxIyEhSmY2Y1I8iLK+HQyeJSFTurTjMda0=; b=OtC+F4y/OElYvElS43LlRGS4KRcz5O4s7qEdyMreb5M13I4ne16W64lFgAhDBc8PP5 3LhsCtcitu30d7e4vZgg9WGop95mFq8wAW22O+aR1zKJg/auWS28Hw5GO1S1p3jLsuib 0wXRcx6onKsqiMusxpaVZeDyx2TO3YbaxS1SU= 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=LJn1ZII4XTMUIQIlSawR7ZfXaBHQFuE8k0rGNia0//j/MrAkVF4dYWvu4Wdgx/6z6S dQdgxYsOz+9sP7Swpb7kxYjvuP/Ge1qkTnXHdTnmzMMetm4yx5TpyziSYDPDf2Ij3xkS +8dNEFCxOipUyXedBtmdqKpySv/+gU9c6/CpA= MIME-Version: 1.0 Received: by 10.239.179.6 with SMTP id b6mr67341hbg.161.1238924159411; Sun, 05 Apr 2009 02:35:59 -0700 (PDT) In-Reply-To: <49D818B1.6050904@gmail.com> References: <49D51906.5030201@free.fr> <49D7827B.10006@gmail.com> <25aac9fc0904041128q73e282b9y30069b76beb048d7@mail.gmail.com> <49D7AC3E.3030403@gmail.com> <25aac9fc0904041257k61ed9151od5860a4ee6e7ace9@mail.gmail.com> <49D818B1.6050904@gmail.com> Date: Sun, 5 Apr 2009 10:35:59 +0100 Message-ID: <25aac9fc0904050235v4839265dk8e2ceeb7b0b8a62a@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 05/04/2009, Phil Steitz wrote: > sebb wrote: > > > 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? > > > > > > > Both. I want to minimize the impact of the upgrade to users. The code already uses some 1.5 features, e.g. enum and autoboxing. It also already uses parameterized types, just not everywhere. I think it's too late for compile-time compatibility with 1.4. Regarding raw types, the types are erased at run-time anyway. I think the only affect on user code would be to generate some compile-time warnings. I don't think it will stop code working. Anyway, the code already uses non-raw types, it's just that some raw types have yet to be converted. > Phil > > > > > > > > > > > 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 > > > > > > > > > --------------------------------------------------------------------- > 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