Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Fri, 3 Aug 2012 22:22:06 +0200
From: Gilles Sadowski <gilles@harfang.homelinux.org>
To: dev@commons.apache.org
Subject: [Math] Towards release 3.1
Message-ID: <20120803202206.GS25337@dusk.harfang.homelinux.org>
Mail-Followup-To: dev@commons.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-DCC-scarlet.be-Metrics: hel 20002; Body=1 Fuz1=1 Fuz2=1
X-Virus-Scanned: clamav-milter 0.97.1-exp at hel
X-Virus-Status: Clean
X-Virus-Checked: Checked by ClamAV on apache.org

Hello.

More than 60 issues have been resolved since the release of Commons Math
3.0.
I think that it is time to lay out a road map for the next release (3.1),
with a target date of early September (at which point, 3.0 will be 6 months
old).

The following issues have been worked on as much as permitted for a minor
release (backwards-compatibility) and thus can be considered resolved w.r.t.
the 3.1 release:
  MATH-825
  MATH-803
  MATH-800
  MATH-799
  MATH-784

The following issues are bugs that do not block the 3.1 release (either they
are minor or they would require semantic changes that are forbidden, or will
be surprising, in a minor release):
  MATH-821
  MATH-788
  MATH-758

The following are the more serious issues:
  MATH-836
  MATH-828
  MATH-819
  MATH-789
  MATH-778
  MATH-740
  MATH-738

"Wish" or "improvement" issues that miss a patch should not be blocking the
3.1 release.
Some of them are still marked with 3.1 as the target version. Please give
your opinion about whether they could be easily implemented in the next few
weeks, or should be postponed to release 3.2 or 4.0.

Some issues have a large scope and would require a re-design of certain
classes (e.g. MATH-765 and related), not to be implemented in a minor
release.

Please review all issues (especially those assigned to you, or reported by
you, or where you took an active part in the discussion) and provide
feedback on their "currentness".


Thanks and best regards,
Gilles

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