Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4F6DF38F.8010406@free.fr>
Date: Sat, 24 Mar 2012 17:17:19 +0100
From: Luc Maisonobe <Luc.Maisonobe@free.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: Commons-Math release schedule
References: 
 <20412_1332496556_4F6C48AC_20412_12801_1_4F6C48B0.9020100@sciops.esa.int>
In-Reply-To: 
 <20412_1332496556_4F6C48AC_20412_12801_1_4F6C48B0.9020100@sciops.esa.int>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

Le -10/01/-28163 20:59, Hassan Siddiqui a �crit :
> Dear Commons-Math developers

Hi Hassan,

> 
> My name is Hassan Siddiqui and I am working on a Java scientific project
> that involves a significant amount of numerical analysis code. There are
> some 300+ developers and scientist involved in this project.

I guess I (and Gilles even more than me) know which project you are
talking about ...

> 
> We are using Commons-Math already to an extent but we do intend to be
> more involved.

Fine.

> 
> But one question I would like to ask is what is the process for
> arranging for a new release of Commons-Math. I ask because we have
> 6-month release schedule for our mathematical and utility library, which
> makes use of Commons Math, and we would like to see whether we can have
> releases of Commons Math that could fit that release cycle.

Yes. We have not been very good at this for the last release and it was
way too late. However, we do want to be more in line with the "release
early, really often" credo.

What is most needed is help in resolving the issues that are registered
in our JIRA tracking system
(<https://issues.apache.org/jira/browse/MATH>). Opening new issues also
help improving the product, of course, but help in solving them is most
wanted.

As far as simple issues are concerned, they can be dicussed on the JIRA
tracker itself, and patches can be attached (not forgetting to check the
box allowing us to include the patch in the main code). Testing the
already provided patch and cleaning them so they do have appropriate
comments, javadocs and test cases helps. When discussion on issues is
too long, it is better to switch the discussion to the developers
mailing list, as it is a more appropriate place for this.

When the component has reached a state where another release is worth
doing, then asking for such a release on the dev list and helping in
freezing the code and polishing it is greatly appreciated.

> 
> We are more than happy to assist in Commons Math releases, if this helps.

Thanks for your help.

Luc

> 
> Regards
> 
> -Hassan.
> 
> 
> 
> This message and any attachments are intended for the use of the
> addressee or addressees only. The unauthorised disclosure, use,
> dissemination or copying (either in whole or in part) of its content is
> not permitted. If you received this message in error, please notify the
> sender and delete it from your system. Emails can be altered and their
> integrity cannot be guaranteed by the sender.
> 
> Please consider the environment before printing this email.
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org