You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by lu...@apache.org on 2016/01/05 22:47:46 UTC

[1/7] [math] added link for 3.6 javadoc.

Repository: commons-math
Updated Branches:
  refs/heads/MATH_3_X 026e33053 -> 838788fd6


added link for 3.6 javadoc.


Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/2525399e
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/2525399e
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/2525399e

Branch: refs/heads/MATH_3_X
Commit: 2525399e1654530f1eff026cf3a16e473cd07296
Parents: 9df7957
Author: Luc Maisonobe <lu...@apache.org>
Authored: Fri Jan 1 14:41:25 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Fri Jan 1 15:13:23 2016 +0100

----------------------------------------------------------------------
 src/site/site.xml | 2 ++
 1 file changed, 2 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-math/blob/2525399e/src/site/site.xml
----------------------------------------------------------------------
diff --git a/src/site/site.xml b/src/site/site.xml
index b6e0f7a..b9adbf4 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -27,6 +27,8 @@
       <item name="Overview" href="/index.html"/>
       <item name="Downloads" href="http://commons.apache.org/math/download_math.cgi"/>
       <item name="Latest API docs (development)" href="apidocs/index.html"/>
+      <item name="Javadoc (3.6 release)"
+         href="http://commons.apache.org/math/javadocs/api-3.6/index.html"/>
       <item name="Javadoc (3.5 release)"
          href="http://commons.apache.org/math/javadocs/api-3.5/index.html"/>
       <item name="Javadoc (3.4.1 release)"


[2/7] [math] Updated download page in preparation for 3.6 release.

Posted by lu...@apache.org.
Updated download page in preparation for 3.6 release.


Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/e3eb0f65
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/e3eb0f65
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/e3eb0f65

Branch: refs/heads/MATH_3_X
Commit: e3eb0f65f0ba89cb427104e6e0a809a773c33e69
Parents: e7e5406
Author: Luc Maisonobe <lu...@apache.org>
Authored: Fri Jan 1 13:29:49 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Fri Jan 1 15:13:23 2016 +0100

----------------------------------------------------------------------
 src/site/xdoc/download_math.xml | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-math/blob/e3eb0f65/src/site/xdoc/download_math.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/download_math.xml b/src/site/xdoc/download_math.xml
index 3e6a093..124cdac 100644
--- a/src/site/xdoc/download_math.xml
+++ b/src/site/xdoc/download_math.xml
@@ -95,32 +95,32 @@ limitations under the License.
       </p>
     </subsection>
     </section>
-    <section name="Apache Commons Math 3.5 (requires Java 1.5+)">
+    <section name="Apache Commons Math 3.6 (requires Java 1.5+)">
       <subsection name="Binaries">
         <table>
           <tr>
-              <td><a href="[preferred]/commons/math/binaries/commons-math3-3.5-bin.tar.gz">commons-math3-3.5-bin.tar.gz</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.5-bin.tar.gz.md5">md5</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.5-bin.tar.gz.asc">pgp</a></td>
+              <td><a href="[preferred]/commons/math/binaries/commons-math3-3.6-bin.tar.gz">commons-math3-3.6-bin.tar.gz</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.6-bin.tar.gz.md5">md5</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.6-bin.tar.gz.asc">pgp</a></td>
           </tr>
           <tr>
-              <td><a href="[preferred]/commons/math/binaries/commons-math3-3.5-bin.zip">commons-math3-3.5-bin.zip</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.5-bin.zip.md5">md5</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.5-bin.zip.asc">pgp</a></td>
+              <td><a href="[preferred]/commons/math/binaries/commons-math3-3.6-bin.zip">commons-math3-3.6-bin.zip</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.6-bin.zip.md5">md5</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/binaries/commons-math3-3.6-bin.zip.asc">pgp</a></td>
           </tr>
         </table>
       </subsection>
       <subsection name="Source">
         <table>
           <tr>
-              <td><a href="[preferred]/commons/math/source/commons-math3-3.5-src.tar.gz">commons-math3-3.5-src.tar.gz</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.5-src.tar.gz.md5">md5</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.5-src.tar.gz.asc">pgp</a></td>
+              <td><a href="[preferred]/commons/math/source/commons-math3-3.6-src.tar.gz">commons-math3-3.6-src.tar.gz</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.6-src.tar.gz.md5">md5</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.6-src.tar.gz.asc">pgp</a></td>
           </tr>
           <tr>
-              <td><a href="[preferred]/commons/math/source/commons-math3-3.5-src.zip">commons-math3-3.5-src.zip</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.5-src.zip.md5">md5</a></td>
-              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.5-src.zip.asc">pgp</a></td>
+              <td><a href="[preferred]/commons/math/source/commons-math3-3.6-src.zip">commons-math3-3.6-src.zip</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.6-src.zip.md5">md5</a></td>
+              <td><a href="http://www.apache.org/dist/commons/math/source/commons-math3-3.6-src.zip.asc">pgp</a></td>
           </tr>
         </table>
       </subsection>


[5/7] [math] Merge branch 'MATH_3_X' into 3.6-release

Posted by lu...@apache.org.
Merge branch 'MATH_3_X' into 3.6-release

Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/47ae2b7c
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/47ae2b7c
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/47ae2b7c

Branch: refs/heads/MATH_3_X
Commit: 47ae2b7c84fba9f4dd857b7c70941ec2ef7e6f39
Parents: 2525399 026e330
Author: Luc Maisonobe <lu...@apache.org>
Authored: Sat Jan 2 19:53:12 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Sat Jan 2 19:53:12 2016 +0100

----------------------------------------------------------------------
 build.xml                                       |  23 +-
 doc/release/release.howto.txt                   |  21 +-
 .../apache/commons/math3/complex/Complex.java   | 154 ++---
 .../math3/random/BitsStreamGenerator.java       |   1 -
 .../apache/commons/math3/util/Precision.java    |  39 +-
 src/site/xdoc/userguide/stat.xml                |   9 +-
 .../commons/math3/complex/ComplexTest.java      |  18 +
 .../EnumeratedIntegerDistributionTest.java      |   5 +-
 .../AbstractAdamsFieldIntegratorTest.java       | 260 --------
 ...ctEmbeddedRungeKuttaFieldIntegratorTest.java | 600 -----------------
 .../AbstractRungeKuttaFieldIntegratorTest.java  | 662 -------------------
 ...ractRungeKuttaFieldStepInterpolatorTest.java | 305 ---------
 .../AdamsBashforthFieldIntegratorTest.java      |   2 +-
 .../AdamsFieldIntegratorAbstractTest.java       | 260 ++++++++
 .../AdamsMoultonFieldIntegratorTest.java        |   2 +-
 ...sicalRungKuttaFieldStepInterpolatorTest.java |   2 +-
 .../ClassicalRungeKuttaFieldIntegratorTest.java |   2 +-
 .../DormandPrince54FieldIntegratorTest.java     |   2 +-
 ...ormandPrince54FieldStepInterpolatorTest.java |   2 +-
 .../DormandPrince853FieldIntegratorTest.java    |   2 +-
 ...rmandPrince853FieldStepInterpolatorTest.java |   2 +-
 ...edRungeKuttaFieldIntegratorAbstractTest.java | 600 +++++++++++++++++
 .../ode/nonstiff/EulerFieldIntegratorTest.java  |   2 +-
 .../EulerFieldStepInterpolatorTest.java         |   2 +-
 .../ode/nonstiff/GillFieldIntegratorTest.java   |   2 +-
 .../nonstiff/GillFieldStepInterpolatorTest.java |   2 +-
 .../HighamHall54FieldIntegratorTest.java        |   2 +-
 .../HighamHall54FieldStepInterpolatorTest.java  |   2 +-
 .../ode/nonstiff/LutherFieldIntegratorTest.java |   2 +-
 .../LutherFieldStepInterpolatorTest.java        |   2 +-
 .../nonstiff/MidpointFieldIntegratorTest.java   |   2 +-
 .../MidpointFieldStepInterpolatorTest.java      |   2 +-
 .../RungeKuttaFieldIntegratorAbstractTest.java  | 662 +++++++++++++++++++
 ...eKuttaFieldStepInterpolatorAbstractTest.java | 305 +++++++++
 .../ThreeEighthesFieldIntegratorTest.java       |   2 +-
 .../ThreeEighthesFieldStepInterpolatorTest.java |   2 +-
 test-jar.xml                                    |  50 +-
 37 files changed, 2006 insertions(+), 2008 deletions(-)
----------------------------------------------------------------------



[3/7] [math] preparing pom for 3.6 release.

Posted by lu...@apache.org.
preparing pom for 3.6 release.


Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/e7e54063
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/e7e54063
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/e7e54063

Branch: refs/heads/MATH_3_X
Commit: e7e5406342ed8302c847e771cd453e3036220e52
Parents: d70c566
Author: Luc Maisonobe <lu...@apache.org>
Authored: Fri Jan 1 13:28:00 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Fri Jan 1 15:13:23 2016 +0100

----------------------------------------------------------------------
 pom.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-math/blob/e7e54063/pom.xml
----------------------------------------------------------------------
diff --git a/pom.xml b/pom.xml
index 302107f..edeacf3 100644
--- a/pom.xml
+++ b/pom.xml
@@ -24,7 +24,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>org.apache.commons</groupId>
   <artifactId>commons-math3</artifactId>
-  <version>3.6-SNAPSHOT</version>
+  <version>3.6</version>
   <name>Apache Commons Math</name>
 
   <inceptionYear>2003</inceptionYear>
@@ -374,9 +374,9 @@
     <!-- This value must reflect the current name of the base package. -->
     <commons.osgi.symbolicName>org.apache.commons.math3</commons.osgi.symbolicName>
     <!-- do not use snapshot suffix here -->
-    <commons.release.version>3.5</commons.release.version>
+    <commons.release.version>3.6</commons.release.version>
     <commons.release.desc>(requires Java 1.5+)</commons.release.desc>
-    <!-- <commons.rc.version>RC1</commons.rc.version> -->
+    <commons.rc.version>RC1</commons.rc.version>
     <commons.binary.suffix>-bin</commons.binary.suffix>
 
     <commons.release.2.version>2.2</commons.release.2.version>


[6/7] [math] Preparing release candidate 2 for Apache Commons Math 3.6.

Posted by lu...@apache.org.
Preparing release candidate 2 for Apache Commons Math 3.6.

Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/95a9d35e
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/95a9d35e
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/95a9d35e

Branch: refs/heads/MATH_3_X
Commit: 95a9d35e77f70ffc9bd5143880c236a760b42005
Parents: 47ae2b7
Author: Luc Maisonobe <lu...@apache.org>
Authored: Sat Jan 2 19:56:59 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Sat Jan 2 19:56:59 2016 +0100

----------------------------------------------------------------------
 pom.xml                 | 2 +-
 src/changes/changes.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-math/blob/95a9d35e/pom.xml
----------------------------------------------------------------------
diff --git a/pom.xml b/pom.xml
index edeacf3..3705a86 100644
--- a/pom.xml
+++ b/pom.xml
@@ -376,7 +376,7 @@
     <!-- do not use snapshot suffix here -->
     <commons.release.version>3.6</commons.release.version>
     <commons.release.desc>(requires Java 1.5+)</commons.release.desc>
-    <commons.rc.version>RC1</commons.rc.version>
+    <commons.rc.version>RC2</commons.rc.version>
     <commons.binary.suffix>-bin</commons.binary.suffix>
 
     <commons.release.2.version>2.2</commons.release.2.version>

http://git-wip-us.apache.org/repos/asf/commons-math/blob/95a9d35e/src/changes/changes.xml
----------------------------------------------------------------------
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 90e8dc9..21ab68f 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -50,7 +50,7 @@ If the output is not quite correct, check for invisible trailing spaces!
     <title>Commons Math Release Notes</title>
   </properties>
   <body>
-    <release version="3.6" date="2016-01-04" description="
+    <release version="3.6" date="2016-01-05" description="
 This is a minor release: It combines bug fixes and new features.
  Changes to existing features were made in a backwards-compatible
  way such as to allow drop-in replacement of the v3.x JAR file.


Re: [Math] Next version(s)? (Was: [...] Putting MATH_3_X branch to post-release state.)

Posted by Phil Steitz <ph...@gmail.com>.
On Wed, Jan 6, 2016 at 10:32 AM, Luc Maisonobe <lu...@spaceroots.org> wrote:

> Le 06/01/2016 15:19, Gilles a écrit :
> > Hi.
>
> Hi Gilles,
>
> >
> > On Tue, 05 Jan 2016 21:47:52 -0000, luc@apache.org wrote:
> >> Putting MATH_3_X branch to post-release state.
> >>
> >> This change is only done in case a new release should be done.
> >> This is however not really expected now and the next release should
> >> rather be 4.0 than 3.7.
> >
> > The latest clash about changes in the "master" branch makes this
> > statement quite non obvious.
>
> I don't think anybody wants to keep 3.X indefinitely. We did start
> a 4.0 branch on master. The fact it doesn't progress fast doesn't
> mean people only want to continue on 3.X.
>

+1
I will likely continue to patch 3.x and even implement new features in that
branch that can be added compatibly.  That does not mean I don't want to
see 4.0 stabilize and get released.  We have a lot of users (yes, I am just
one of them, but I respectfully reserve the right to stand up for others
who do not participate here) on 3.x and at this point it is not clear how
much API breakage there is going to be in 4, so as long as it is easy to do
so, I plan to backport the patches I work on to 3.x.


>
> >
> > Can we, for once, have a real release policy put in place?
> > A policy that would be based on requirements transparently laid out?
> >
> > That would imply that a *zero* weight would be assigned to statements
> > made in order to represent an anonymous ("the users") group (that cannot
> > participate in the debate, as per "Your role at the ASF is one assigned
> > to you personally, [...]".)
> >
> > Of course, each developer is a user (*one* user).
> > Of course, each developer is entitled to his own idea of what CM is,
> > should be, or should not be (and the consequence thereof on the
> > project's management); but that should be clearly spelled out as one
> > opinion, on a par with any other developer's opinion.
>
> What I wrote or commit is only one people writings or work and was never
> stated as an overall meta opinion. When I speak about users, I speak
> about the users I know of, which are mainly my coworkers. Count it
> as one opinion only if you want and associate it to me only if you
> want. It is not intended to be considered as more or less important
> than others opinions. Putting zero weight to it arbitrarily is not
> better than putting a 10x weight on it.
>
> >
> > A useful policy will help in avoiding that high level questions
> > (such as "Backwards-compatibility or not?") constantly pollute
> > development issues (such as "Refactor <this code>").
> >
> > The policy should also include a plan for releases, so that we don't
> > have to wait until Luc needs one in a hurry, in order to prepare the
> > next release.
>
> We never waited until I need it. Anybody can perform release. Any
> contributor can ask for a release. I happened for other commons
> sub-project, and sometimes was done, sometimes not. The main
> point was always: is there someone available that volunteers to
> take the pain of the release. Each time I asked for a release, I
> do volunteer to do it. Here again, it could have been anybody instead
> of me.
>
> We all want to Release Early Release Often, and we all fail to do it
> because sincerely, it is a pain. So we end up doing release irregularly.
>
> We are not in a corporate environment when a manager can dictate rules
> that must be obeyed. This is a voluntary-based project. So even if we
> were to decide some fixed rules, with high level requirement or fixed
> release plans, we would never follow these plans in reality. We already
> said quite a number of times: we should release more often. We never
> succeeded to do it effectively.
>

+1
Your great work documenting the release process is a big help.  The way it
has always worked in Commons is someone proposes to make a release,
presents a plan, volunteers to do it, and cuts the release.  Yes, it is a
lot of work.  Yes, we don't do it enough.  But the challenge is almost
never agreeing on release contents.  Sometimes our desires are bigger than
our ability to get things done in the scope of a single release and it ends
up taking us a long time; but I don't think the answer is to impose a
schedule or add more rules.  Good automation and keeping code close to
"releasable" on our main lines is the best thing we can do, IMO.  The
branching model discussed else-thread should help with the second of these.



>
> >
> > Most importantly, we must know what are the requirements in order to
> > start to manage this project in any sensible way.
> > In particular, a policy should prevent to informally come back on
> > previous formal decisions, with its trail of "draining" discussions.
>
> So we should have minutes of decisions, with a signature of all
> participants, and some regular meetings to monitor progress. And what
> about a penalty if we don't meet deadline? Oh, and of course we should
> nominate a manager, and have an independent quality management to
> oversee what we do and check we really stick to the rules. We should
> probably write some specification documents, and interface control
> documents, and preliminary design documents, detailed design also,
> and probably some test plans and development guidelines ... and we
> should get paid.
>
> Of course I go to the extreme here, and the paragraph above is
> expected to be read as humorous. What I want to point out is
> that in a community and collaborative development (yes, I really
> mean it *is* collaborative and we succeed in it), rules are fuzzy,
> and followed if they are natural enough that they are not really
> rules.
>

I will again quote gstein (who does not remember saying exactly this),
"rules that people follow are needless; rules that people don't follow
don't work"

I expect your TPS report tomorrow AM, Luc :)

Phil




>
> >
> > Do the above points seem a common starting ground?
>
> As long as these are fuzzy rules, yes. If they are strong policy
> in a corporate-like management, no.
>
> >
> > If so, we can begin to list the issues which the policy should aim
> > at answering.
> > I'd start with the following:
> >  * Release early, release often (and what it means, in practice,
> >    for CM)
>
> Big +1. Hey, we already want that. It is just that saying it
> won't make it appear magically. Someone has to take the pain.
>
> >  * Several development targets or a single one? [Depends on which
> >    are the "requirements".]
>
> I don't understand what you mean here.
>
> >
> > To make things clearer, we could first work on a template of questions
> > whose answers would help in defining the various directions which the
> > CM developers are interested in.  And then we'll have to decide which
> > project direction(s) the PMC wants to and/or is able to handle.
> >
> > No policy (or several "personal" policies, a.k.a. hidden agenda) is
> > what _really_ drains this "community".
>
> Strong policy (or inflexible policy, a.k.a. corporate management) is
> what would explode this community.
>
> best regards,
> Luc
>
> >
> >
> > Regards,
> > Gilles
> >
> >> [...]
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
>

Re: [Math] Next version(s)? (Was: [...] Putting MATH_3_X branch to post-release state.)

Posted by Phil Steitz <ph...@gmail.com>.

> On Wed, Jan 6, 2016 at 11:07 AM, Gilles <gi...@harfang.homelinux.org> wrote:
> Hi Luc.
> 
>> On Wed, 6 Jan 2016 18:32:37 +0100, Luc Maisonobe wrote:
>> Le 06/01/2016 15:19, Gilles a écrit :
>>> Hi.
>> 
>> Hi Gilles,
>> 
>>> 
>>>> On Tue, 05 Jan 2016 21:47:52 -0000, luc@apache.org wrote:
>>>> Putting MATH_3_X branch to post-release state.
>>>> 
>>>> This change is only done in case a new release should be done.
>>>> This is however not really expected now and the next release should
>>>> rather be 4.0 than 3.7.
>>> 
>>> The latest clash about changes in the "master" branch makes this
>>> statement quite non obvious.
>> 
>> I don't think anybody wants to keep 3.X indefinitely. We did start
>> a 4.0 branch on master. The fact it doesn't progress fast doesn't
>> mean people only want to continue on 3.X.
>> 
>>> 
>>> Can we, for once, have a real release policy put in place?
>>> A policy that would be based on requirements transparently laid out?
>>> 
>>> That would imply that a *zero* weight would be assigned to statements
>>> made in order to represent an anonymous ("the users") group (that cannot
>>> participate in the debate, as per "Your role at the ASF is one assigned
>>> to you personally, [...]".)
>>> 
>>> Of course, each developer is a user (*one* user).
>>> Of course, each developer is entitled to his own idea of what CM is,
>>> should be, or should not be (and the consequence thereof on the
>>> project's management); but that should be clearly spelled out as one
>>> opinion, on a par with any other developer's opinion.
>> 
>> What I wrote or commit is only one people writings or work and was never
>> stated as an overall meta opinion. When I speak about users, I speak
>> about the users I know of, which are mainly my coworkers. Count it
>> as one opinion only if you want and associate it to me only if you
>> want. It is not intended to be considered as more or less important
>> than others opinions. Putting zero weight to it arbitrarily is not
>> better than putting a 10x weight on it.
> 
> I meant that a statement like "I want this or that" gets weight one.
> A statement that says "The users want this or that" gets zero weight.
> 
> So, yes, 1 + 0 = 1, if you like.
> 
>>> 
>>> A useful policy will help in avoiding that high level questions
>>> (such as "Backwards-compatibility or not?") constantly pollute
>>> development issues (such as "Refactor <this code>").
>>> 
>>> The policy should also include a plan for releases, so that we don't
>>> have to wait until Luc needs one in a hurry, in order to prepare the
>>> next release.
>> 
>> We never waited until I need it. Anybody can perform release. Any
>> contributor can ask for a release. I happened for other commons
>> sub-project, and sometimes was done, sometimes not. The main
>> point was always: is there someone available that volunteers to
>> take the pain of the release. Each time I asked for a release, I
>> do volunteer to do it. Here again, it could have been anybody instead
>> of me.
> 
> You got what I meant in reverse: it is fortunate that you need a release
> once in a while because otherwise, there would be none.
> 
> What I propose is that we decide to release more often and prepare the
> release at the deadline (unless there was no development of course).
> 
>> 
>> We all want to Release Early Release Often, and we all fail to do it
>> because sincerely, it is a pain. So we end up doing release irregularly.
>> 
>> We are not in a corporate environment when a manager can dictate rules
>> that must be obeyed. This is a voluntary-based project. So even if we
>> were to decide some fixed rules, with high level requirement or fixed
>> release plans, we would never follow these plans in reality. We already
>> said quite a number of times: we should release more often. We never
>> succeeded to do it effectively.
>> 
>>> 
>>> Most importantly, we must know what are the requirements in order to
>>> start to manage this project in any sensible way.
>>> In particular, a policy should prevent to informally come back on
>>> previous formal decisions, with its trail of "draining" discussions.
>> 
>> So we should have minutes of decisions, with a signature of all
>> participants, and some regular meetings to monitor progress. And what
>> about a penalty if we don't meet deadline? Oh, and of course we should
>> nominate a manager, and have an independent quality management to
>> oversee what we do and check we really stick to the rules. We should
>> probably write some specification documents, and interface control
>> documents, and preliminary design documents, detailed design also,
>> and probably some test plans and development guidelines ... and we
>> should get paid.
>> 
>> Of course I go to the extreme here, and the paragraph above is
>> expected to be read as humorous. What I want to point out is
>> that in a community and collaborative development (yes, I really
>> mean it *is* collaborative and we succeed in it), rules are fuzzy,
>> and followed if they are natural enough that they are not really
>> rules.
>> 
>>> 
>>> Do the above points seem a common starting ground?
>> 
>> As long as these are fuzzy rules, yes. If they are strong policy
>> in a corporate-like management, no.
>> 
>>> 
>>> If so, we can begin to list the issues which the policy should aim
>>> at answering.
>>> I'd start with the following:
>>>  * Release early, release often (and what it means, in practice,
>>>    for CM)
>> 
>> Big +1. Hey, we already want that. It is just that saying it
>> won't make it appear magically. Someone has to take the pain.
>> 
>>>  * Several development targets or a single one? [Depends on which
>>>    are the "requirements".]
>> 
>> I don't understand what you mean here.
> 
> One possibility is to want to keep both
> * a long-term compatible line of development (or just bug-fix), and
> * a cutting-edge line of development
> 
> To be clear:
> In the first line, we can keep all the cruft and Java 5...
> In the second line, we do current Java programming and break everything
> as often as we fancy. ;-)
> 
> There can be additional middle-ground lines with adapter layers.
> 
>>> 
>>> To make things clearer, we could first work on a template of questions
>>> whose answers would help in defining the various directions which the
>>> CM developers are interested in.  And then we'll have to decide which
>>> project direction(s) the PMC wants to and/or is able to handle.
>>> 
>>> No policy (or several "personal" policies, a.k.a. hidden agenda) is
>>> what _really_ drains this "community".
>> 
>> Strong policy (or inflexible policy, a.k.a. corporate management) is
>> what would explode this community.
> 
> I don't see it as viable that the unnamed policy in force is compatibility
> (far, far, far) above all else.
> 
> Regards,
> Gilles
> 
>> 
>> 
>> best regards,
>> Luc
>> 
>>> 
>>> 
>>> Regards,
>>> Gilles
>>> 
>>>> [...]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org


Re: [Math] Next version(s)? (Was: [...] Putting MATH_3_X branch to post-release state.)

Posted by Gilles <gi...@harfang.homelinux.org>.
Hi Luc.

On Wed, 6 Jan 2016 18:32:37 +0100, Luc Maisonobe wrote:
> Le 06/01/2016 15:19, Gilles a écrit :
>> Hi.
>
> Hi Gilles,
>
>>
>> On Tue, 05 Jan 2016 21:47:52 -0000, luc@apache.org wrote:
>>> Putting MATH_3_X branch to post-release state.
>>>
>>> This change is only done in case a new release should be done.
>>> This is however not really expected now and the next release should
>>> rather be 4.0 than 3.7.
>>
>> The latest clash about changes in the "master" branch makes this
>> statement quite non obvious.
>
> I don't think anybody wants to keep 3.X indefinitely. We did start
> a 4.0 branch on master. The fact it doesn't progress fast doesn't
> mean people only want to continue on 3.X.
>
>>
>> Can we, for once, have a real release policy put in place?
>> A policy that would be based on requirements transparently laid out?
>>
>> That would imply that a *zero* weight would be assigned to 
>> statements
>> made in order to represent an anonymous ("the users") group (that 
>> cannot
>> participate in the debate, as per "Your role at the ASF is one 
>> assigned
>> to you personally, [...]".)
>>
>> Of course, each developer is a user (*one* user).
>> Of course, each developer is entitled to his own idea of what CM is,
>> should be, or should not be (and the consequence thereof on the
>> project's management); but that should be clearly spelled out as one
>> opinion, on a par with any other developer's opinion.
>
> What I wrote or commit is only one people writings or work and was 
> never
> stated as an overall meta opinion. When I speak about users, I speak
> about the users I know of, which are mainly my coworkers. Count it
> as one opinion only if you want and associate it to me only if you
> want. It is not intended to be considered as more or less important
> than others opinions. Putting zero weight to it arbitrarily is not
> better than putting a 10x weight on it.

I meant that a statement like "I want this or that" gets weight one.
A statement that says "The users want this or that" gets zero weight.

So, yes, 1 + 0 = 1, if you like.

>>
>> A useful policy will help in avoiding that high level questions
>> (such as "Backwards-compatibility or not?") constantly pollute
>> development issues (such as "Refactor <this code>").
>>
>> The policy should also include a plan for releases, so that we don't
>> have to wait until Luc needs one in a hurry, in order to prepare the
>> next release.
>
> We never waited until I need it. Anybody can perform release. Any
> contributor can ask for a release. I happened for other commons
> sub-project, and sometimes was done, sometimes not. The main
> point was always: is there someone available that volunteers to
> take the pain of the release. Each time I asked for a release, I
> do volunteer to do it. Here again, it could have been anybody instead
> of me.

You got what I meant in reverse: it is fortunate that you need a 
release
once in a while because otherwise, there would be none.

What I propose is that we decide to release more often and prepare the
release at the deadline (unless there was no development of course).

>
> We all want to Release Early Release Often, and we all fail to do it
> because sincerely, it is a pain. So we end up doing release 
> irregularly.
>
> We are not in a corporate environment when a manager can dictate 
> rules
> that must be obeyed. This is a voluntary-based project. So even if we
> were to decide some fixed rules, with high level requirement or fixed
> release plans, we would never follow these plans in reality. We 
> already
> said quite a number of times: we should release more often. We never
> succeeded to do it effectively.
>
>>
>> Most importantly, we must know what are the requirements in order to
>> start to manage this project in any sensible way.
>> In particular, a policy should prevent to informally come back on
>> previous formal decisions, with its trail of "draining" discussions.
>
> So we should have minutes of decisions, with a signature of all
> participants, and some regular meetings to monitor progress. And what
> about a penalty if we don't meet deadline? Oh, and of course we 
> should
> nominate a manager, and have an independent quality management to
> oversee what we do and check we really stick to the rules. We should
> probably write some specification documents, and interface control
> documents, and preliminary design documents, detailed design also,
> and probably some test plans and development guidelines ... and we
> should get paid.
>
> Of course I go to the extreme here, and the paragraph above is
> expected to be read as humorous. What I want to point out is
> that in a community and collaborative development (yes, I really
> mean it *is* collaborative and we succeed in it), rules are fuzzy,
> and followed if they are natural enough that they are not really
> rules.
>
>>
>> Do the above points seem a common starting ground?
>
> As long as these are fuzzy rules, yes. If they are strong policy
> in a corporate-like management, no.
>
>>
>> If so, we can begin to list the issues which the policy should aim
>> at answering.
>> I'd start with the following:
>>  * Release early, release often (and what it means, in practice,
>>    for CM)
>
> Big +1. Hey, we already want that. It is just that saying it
> won't make it appear magically. Someone has to take the pain.
>
>>  * Several development targets or a single one? [Depends on which
>>    are the "requirements".]
>
> I don't understand what you mean here.

One possibility is to want to keep both
* a long-term compatible line of development (or just bug-fix), and
* a cutting-edge line of development

To be clear:
In the first line, we can keep all the cruft and Java 5...
In the second line, we do current Java programming and break everything
as often as we fancy. ;-)

There can be additional middle-ground lines with adapter layers.

>>
>> To make things clearer, we could first work on a template of 
>> questions
>> whose answers would help in defining the various directions which 
>> the
>> CM developers are interested in.  And then we'll have to decide 
>> which
>> project direction(s) the PMC wants to and/or is able to handle.
>>
>> No policy (or several "personal" policies, a.k.a. hidden agenda) is
>> what _really_ drains this "community".
>
> Strong policy (or inflexible policy, a.k.a. corporate management) is
> what would explode this community.

I don't see it as viable that the unnamed policy in force is 
compatibility
(far, far, far) above all else.

Regards,
Gilles

>
>
> best regards,
> Luc
>
>>
>>
>> Regards,
>> Gilles
>>
>>> [...]


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


Re: [Math] Next version(s)? (Was: [...] Putting MATH_3_X branch to post-release state.)

Posted by Luc Maisonobe <lu...@spaceroots.org>.
Le 06/01/2016 15:19, Gilles a écrit :
> Hi.

Hi Gilles,

> 
> On Tue, 05 Jan 2016 21:47:52 -0000, luc@apache.org wrote:
>> Putting MATH_3_X branch to post-release state.
>>
>> This change is only done in case a new release should be done.
>> This is however not really expected now and the next release should
>> rather be 4.0 than 3.7.
> 
> The latest clash about changes in the "master" branch makes this
> statement quite non obvious.

I don't think anybody wants to keep 3.X indefinitely. We did start
a 4.0 branch on master. The fact it doesn't progress fast doesn't
mean people only want to continue on 3.X.

> 
> Can we, for once, have a real release policy put in place?
> A policy that would be based on requirements transparently laid out?
> 
> That would imply that a *zero* weight would be assigned to statements
> made in order to represent an anonymous ("the users") group (that cannot
> participate in the debate, as per "Your role at the ASF is one assigned
> to you personally, [...]".)
> 
> Of course, each developer is a user (*one* user).
> Of course, each developer is entitled to his own idea of what CM is,
> should be, or should not be (and the consequence thereof on the
> project's management); but that should be clearly spelled out as one
> opinion, on a par with any other developer's opinion.

What I wrote or commit is only one people writings or work and was never
stated as an overall meta opinion. When I speak about users, I speak
about the users I know of, which are mainly my coworkers. Count it
as one opinion only if you want and associate it to me only if you
want. It is not intended to be considered as more or less important
than others opinions. Putting zero weight to it arbitrarily is not
better than putting a 10x weight on it.

> 
> A useful policy will help in avoiding that high level questions
> (such as "Backwards-compatibility or not?") constantly pollute
> development issues (such as "Refactor <this code>").
> 
> The policy should also include a plan for releases, so that we don't
> have to wait until Luc needs one in a hurry, in order to prepare the
> next release.

We never waited until I need it. Anybody can perform release. Any
contributor can ask for a release. I happened for other commons
sub-project, and sometimes was done, sometimes not. The main
point was always: is there someone available that volunteers to
take the pain of the release. Each time I asked for a release, I
do volunteer to do it. Here again, it could have been anybody instead
of me.

We all want to Release Early Release Often, and we all fail to do it
because sincerely, it is a pain. So we end up doing release irregularly.

We are not in a corporate environment when a manager can dictate rules
that must be obeyed. This is a voluntary-based project. So even if we
were to decide some fixed rules, with high level requirement or fixed
release plans, we would never follow these plans in reality. We already
said quite a number of times: we should release more often. We never
succeeded to do it effectively.

> 
> Most importantly, we must know what are the requirements in order to
> start to manage this project in any sensible way.
> In particular, a policy should prevent to informally come back on
> previous formal decisions, with its trail of "draining" discussions.

So we should have minutes of decisions, with a signature of all
participants, and some regular meetings to monitor progress. And what
about a penalty if we don't meet deadline? Oh, and of course we should
nominate a manager, and have an independent quality management to
oversee what we do and check we really stick to the rules. We should
probably write some specification documents, and interface control
documents, and preliminary design documents, detailed design also,
and probably some test plans and development guidelines ... and we
should get paid.

Of course I go to the extreme here, and the paragraph above is
expected to be read as humorous. What I want to point out is
that in a community and collaborative development (yes, I really
mean it *is* collaborative and we succeed in it), rules are fuzzy,
and followed if they are natural enough that they are not really
rules.

> 
> Do the above points seem a common starting ground?

As long as these are fuzzy rules, yes. If they are strong policy
in a corporate-like management, no.

> 
> If so, we can begin to list the issues which the policy should aim
> at answering.
> I'd start with the following:
>  * Release early, release often (and what it means, in practice,
>    for CM)

Big +1. Hey, we already want that. It is just that saying it
won't make it appear magically. Someone has to take the pain.

>  * Several development targets or a single one? [Depends on which
>    are the "requirements".]

I don't understand what you mean here.

> 
> To make things clearer, we could first work on a template of questions
> whose answers would help in defining the various directions which the
> CM developers are interested in.  And then we'll have to decide which
> project direction(s) the PMC wants to and/or is able to handle.
> 
> No policy (or several "personal" policies, a.k.a. hidden agenda) is
> what _really_ drains this "community".

Strong policy (or inflexible policy, a.k.a. corporate management) is
what would explode this community.

best regards,
Luc

> 
> 
> Regards,
> Gilles
> 
>> [...]
> 
> 
> ---------------------------------------------------------------------
> 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


[Math] Next version(s)? (Was: [...] Putting MATH_3_X branch to post-release state.)

Posted by Gilles <gi...@harfang.homelinux.org>.
Hi.

On Tue, 05 Jan 2016 21:47:52 -0000, luc@apache.org wrote:
> Putting MATH_3_X branch to post-release state.
>
> This change is only done in case a new release should be done.
> This is however not really expected now and the next release should
> rather be 4.0 than 3.7.

The latest clash about changes in the "master" branch makes this
statement quite non obvious.

Can we, for once, have a real release policy put in place?
A policy that would be based on requirements transparently laid out?

That would imply that a *zero* weight would be assigned to statements
made in order to represent an anonymous ("the users") group (that 
cannot
participate in the debate, as per "Your role at the ASF is one assigned
to you personally, [...]".)

Of course, each developer is a user (*one* user).
Of course, each developer is entitled to his own idea of what CM is,
should be, or should not be (and the consequence thereof on the
project's management); but that should be clearly spelled out as one
opinion, on a par with any other developer's opinion.

A useful policy will help in avoiding that high level questions
(such as "Backwards-compatibility or not?") constantly pollute
development issues (such as "Refactor <this code>").

The policy should also include a plan for releases, so that we don't
have to wait until Luc needs one in a hurry, in order to prepare the
next release.

Most importantly, we must know what are the requirements in order to
start to manage this project in any sensible way.
In particular, a policy should prevent to informally come back on
previous formal decisions, with its trail of "draining" discussions.

Do the above points seem a common starting ground?

If so, we can begin to list the issues which the policy should aim
at answering.
I'd start with the following:
  * Release early, release often (and what it means, in practice,
    for CM)
  * Several development targets or a single one? [Depends on which
    are the "requirements".]

To make things clearer, we could first work on a template of questions
whose answers would help in defining the various directions which the
CM developers are interested in.  And then we'll have to decide which
project direction(s) the PMC wants to and/or is able to handle.

No policy (or several "personal" policies, a.k.a. hidden agenda) is
what _really_ drains this "community".


Regards,
Gilles

> [...]


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


[7/7] [math] Putting MATH_3_X branch to post-release state.

Posted by lu...@apache.org.
Putting MATH_3_X branch to post-release state.

This change is only done in case a new release should be done.
This is however not really expected now and the next release should
rather be 4.0 than 3.7.

Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/838788fd
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/838788fd
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/838788fd

Branch: refs/heads/MATH_3_X
Commit: 838788fd6302d6cc91e1743144e0f14b71e4812e
Parents: 95a9d35
Author: Luc Maisonobe <lu...@apache.org>
Authored: Tue Jan 5 22:46:13 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Tue Jan 5 22:46:13 2016 +0100

----------------------------------------------------------------------
 doap_math.rdf           | 5 +++++
 pom.xml                 | 2 +-
 src/changes/changes.xml | 2 ++
 3 files changed, 8 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-math/blob/838788fd/doap_math.rdf
----------------------------------------------------------------------
diff --git a/doap_math.rdf b/doap_math.rdf
index a728234..077eb81 100644
--- a/doap_math.rdf
+++ b/doap_math.rdf
@@ -38,6 +38,11 @@
     <release>
       <Version>
         <name>commons-math</name>
+        <created>2016-01-05</created>
+        <revision>3.6</revision>
+      </Version>
+      <Version>
+        <name>commons-math</name>
         <created>2015-04-17</created>
         <revision>3.5</revision>
       </Version>

http://git-wip-us.apache.org/repos/asf/commons-math/blob/838788fd/pom.xml
----------------------------------------------------------------------
diff --git a/pom.xml b/pom.xml
index 3705a86..4153bff 100644
--- a/pom.xml
+++ b/pom.xml
@@ -24,7 +24,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>org.apache.commons</groupId>
   <artifactId>commons-math3</artifactId>
-  <version>3.6</version>
+  <version>3.7-SNAPSHOT</version>
   <name>Apache Commons Math</name>
 
   <inceptionYear>2003</inceptionYear>

http://git-wip-us.apache.org/repos/asf/commons-math/blob/838788fd/src/changes/changes.xml
----------------------------------------------------------------------
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 21ab68f..d9a8b46 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -50,6 +50,8 @@ If the output is not quite correct, check for invisible trailing spaces!
     <title>Commons Math Release Notes</title>
   </properties>
   <body>
+    <release version="3.7" date="TBD" description="TBD">
+    </release>
     <release version="3.6" date="2016-01-05" description="
 This is a minor release: It combines bug fixes and new features.
  Changes to existing features were made in a backwards-compatible


[4/7] [math] Added release notes for 3.6.

Posted by lu...@apache.org.
Added release notes for 3.6.


Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-math/commit/9df79570
Tree: http://git-wip-us.apache.org/repos/asf/commons-math/tree/9df79570
Diff: http://git-wip-us.apache.org/repos/asf/commons-math/diff/9df79570

Branch: refs/heads/MATH_3_X
Commit: 9df79570ae9415ff1a17f0fe6f280f17303e7e51
Parents: e3eb0f6
Author: Luc Maisonobe <lu...@apache.org>
Authored: Fri Jan 1 13:52:16 2016 +0100
Committer: Luc Maisonobe <lu...@apache.org>
Committed: Fri Jan 1 15:13:23 2016 +0100

----------------------------------------------------------------------
 RELEASE-NOTES.txt       | 117 ++++++++++++++++++++++++++++++++++++-------
 src/changes/changes.xml |  28 ++++++++++-
 2 files changed, 126 insertions(+), 19 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-math/blob/9df79570/RELEASE-NOTES.txt
----------------------------------------------------------------------
diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt
index 6a6ac4e..56e8d19 100644
--- a/RELEASE-NOTES.txt
+++ b/RELEASE-NOTES.txt
@@ -1,4 +1,4 @@
-The Apache Commons Math team is pleased to announce the commons-math3-3.5 release!
+The Apache Commons Math team is pleased to announce the commons-math3-3.6 release!
 
 The Apache Commons Math project is a library of lightweight, self-contained mathematics
 and statistics components addressing the most common practical problems not immediately
@@ -7,27 +7,108 @@ available in the Java programming language or commons-lang.
 Changes in this version include:
 
 New features:
-o Added a way to build polyhedrons sets from a list of vertices and
-        facets specified using vertices indices. 
-o Simplified "FastMath#exp(double)" in order to avoid a potential
-        Java 1.5 JIT bug when calling with negative infinity as argument.  Issue: MATH-1198. 
-o Added method "getQuadraticMean()" to "DescriptiveStatistics"
-        and "SummaryStatistics" which calculates the root mean square.  Issue: MATH-1199. 
+o Added a RotationConvention enumerate to allow specifying the semantics
+        or axis/angle for rotations. This enumerate has two values:
+        VECTOR_OPERATOR and FRAME_TRANSFORM.  Issue: MATH-1302,MATH-1303.
+o Added a field-based version of Ordinary Differential Equations framework.
+        This allows integrating ode that refer to RealField elements instead of
+        primitive double, hence opening the way to use DerivativeStructure to
+        compute partial differential without using variational equations, or to solve
+        ode with extended precision using Dfp.  Issue: MATH-1288.
+o Added a nth order Brent solver for general real fields, replacing the former
+        solver that was restricted to Dfp fields only.
+o New "Range" inner class of "o.a.c.m.util.IntegerSequence".  Issue: MATH-1286.
+o "AggregateSummaryStatistics" can now aggregate any kind of
+        "StatisticalSummary".  Issue: MATH-837.
+o Deep copy of "Network" (package "o.a.c.m.ml.neuralnet") to allow evaluation of
+        of intermediate states during training.  Issue: MATH-1278.
+o Added negative zero support in FastMath.pow.  Issue: MATH-1273. Thanks to Qualtagh.
+o Various SOFM visualizations (in package "o.a.c.m.ml.neuralnet.twod.util"):
+        Unified distance matrix, hit histogram, smoothed data histograms,
+        topographic error, quantization error.  Issue: MATH-1270.
+o New interfaces to be implemented by algorithms that visualizes properties
+        of a "NeuronSquareMesh2D" (package "o.a.c.m.ml.neuralnet.twod.util").  Issue: MATH-1268.
+o Reimplemented pow(double, double) in FastMath, for better accuracy in
+        integral power cases and trying to fix erroneous JIT optimization again.
+o Added a pow(double, long) method in FastMath.
+o "NeuronSquareMesh2D" (package "o.a.c.m.ml.neuralnet.twod") implements "Iterable".  Issue: MATH-1265.
+o "MapUtils" (package "o.a.c.m.ml.neuralnet"): Method to sort units according to distance
+        from a given vector.  Issue: MATH-1264.
+o Accessor (class "o.a.c.m.ml.neuralnet.twod.NeuronSquareMesh2D").  Issue: MATH-1263.
+o New "IntegerSequence" class (in package "o.a.c.m.util") with "Incrementor" inner class.  Issue: MATH-1259.
+o "Neuron" class (package "o.a.c.m.ml.neuralnet"): added methods that can be used
+        to assess concurrency performance.  Issue: MATH-1250.
+o Method "cosAngle" in "o.a.c.m.util.MathArrays".  Issue: MATH-1244.
 
 Fixed Bugs:
-o Moved FastMathTestPerformance out of the main test tree, as is is
-        a benchmark rather than a test.  Issue: MATH-1195. 
-o Fixed ignored method parameters in QRDecomposition protected methods.  Issue: MATH-1191. 
-o Fixed wrong selection of line/polyhedron intersection point.  Issue: MATH-1211. Thanks to Mike Zimmerman. 
-o Improved fix for corner cases in BSP-tree merging, when cut sub-hyperplanes vanish.  Issue: MATH-1162. 
-o Fixed link to algorithm description in "PoissonDistribution#sample()".  Issue: MATH-1209. Thanks to Jonathan Ogilvie. 
-o EmpiricalDistribution cumulativeProbability can return NaN when evaluated within a constant bin.  Issue: MATH-1208. 
-o EmpiricalDistribution getKernel fails for buckets with only multiple instances of the same value.  Issue: MATH-1203. 
-o "UnivariateSolverUtils#bracket(...)" sometimes failed to bracket
-        if a reached the lower bound.  Issue: MATH-1204. 
+o Improved performance and accuracy of 2-sample KolmogorovSmirnov tests.  Issue: MATH-1310.
+o Detect start failures with multi-step ODE integrators.  Issue: MATH-1297.
+o Fixed stability issues with Adams-Bashforth and Adams-Moulton ODE integrators.
+        The integrators did not estimate the local error properly and were sometimes
+        stuck attempting to reduce indefinitely the step size as they thought the
+        error was too high. Thanks to Julien Queyrel.
+o Increased default value for number of allowed evaluations in
+        "o.a.c.m.optim.univariate.BracketFinder".  Issue: MATH-1295. Thanks to Luke Lindsay.
+o Fixed potential race condition in PolynomialUtils#buildPolynomial in
+        case polynomials are generated from multiple threads. Furthermore, the
+        synchronization is now performed on the coefficient list instead of the class.  Issue: MATH-1294. Thanks to Kamil Włodarczyk.
+o Fixed FastMath.exp that potentially returned NaN for non-NaN argument.  Issue: MATH-1269.
+o Updated reference in ZipfDistribution's javadoc.  Issue: MATH-1285. Thanks to Pim van der Hoorn.
+o Fixed "Gamma#gamma(double)" for negative values smaller than -20.  Issue: MATH-1283. Thanks to Jean Noel Delavalade.
+o Fixed javadoc of methods {floorDiv,floorMod} in class "FastMath".  Issue: MATH-1237. Thanks to Ken Williams.
+o Check precondition (class "o.a.c.m.random.EmpiricalDistribution").  Issue: MATH-1279.
+o Fixed incorrect Kendall's tau coefficient calculation due to internal integer overflow.  Issue: MATH-1277. Thanks to Marc Rosen.
+o Fixed split/side inconsistencies in BSP trees.  Issue: MATH-1266.
+o Avoid overflow in "Fraction" (multiplication or division by an int).  Issue: MATH-1261. Thanks to Osamu Ikeuchi.
+o Added check for equal array lengths to distance measure functions.  Issue: MATH-1258. Thanks to Gunel Jahangirova.
+o Better accuracy in computation of cumulative probability of "NormalDistribution"
+        (package "o.a.c.m.distribution").  Issue: MATH-1257. Thanks to Bill Murphy.
+o Boundary check to construct an "Interval" (package "o.a.c.m.geometry.euclidean.oned").  Issue: MATH-1256.
+o Wrong neighbourhood size in class "KohonenUpdateAction" (package "o.a.c.m.ml.neuralnet.sofm").  Issue: MATH-1255.
+o ResizableDoubleArray constructor does not work with double array of size 1.  Issue: MATH-1252. Thanks to John Bay.
+o Fixed initial value of "number of calls" counter in class "KohonenUpdateAction"
+        (package "o.a.c.m.ml.neuralnet.sofm").  Issue: MATH-1251.
+o Removed unnecessary allocations in "BigFraction" (package "o.a.c.m.fraction").  Issue: MATH-1248. Thanks to Chris Popp.
+o Fixed error in computing discrete distribution of D statistics for small-sample
+        2-sample Kolmogorov-Smirnov tests. Error was causing incorrect p-values returned
+        by exactP and monteCarloP methods (used by default for small, mid-size samples).  Issue: MATH-1245.
+o "KolmogorovSmirnovTest#ksSum(...)" returned wrong result in case the provided
+        t-parameters was zero. This affected the calculation of "approximateP(...)" for
+        identical samples.  Issue: MATH-1240.
+o Improved performance to calculate the two-sample Kolmogorov-Smirnov test
+        via monte carlo simulation ("KolmogorovSmirnovTets#monteCarloP(...)").  Issue: MATH-1242. Thanks to Otmar Ertl.
+o A "StackOverflowException" was thrown when passing Double.NaN or infinity
+        to "Gamma#digamma(double)" or "Gamma#trigamma(double)". Now the input value
+        is propagated to the output if it is not a real number.  Issue: MATH-1241. Thanks to Aleksei Dievskii.
+o Improved performance of calculating the two-sample Kolmogorov-Smirnov
+        test statistic.  Issue: MATH-1232. Thanks to Otmar Ertl.
+o Fixed error message for unknown parameter name in ODE.  Issue: MATH-1232.
+o Fixed wrong event detection in case of close events pairs.  Issue: MATH-1226.
+o Fix potential branching errors in "FastMath#pow(double, double)" when
+        passing special values, i.e. infinity, due to erroneous JIT optimization.
+o Fixed equals/hashcode contract failure for Dfp.  Issue: MATH-1118.
+o Fixed wrong splitting of huge number in extended accuracy algorithms.  Issue: MATH-1223.
+o Improve performance of "BetaDistribution#sample()" by using Cheng's algorithm.  Issue: MATH-1153. Thanks to Sergei Lebedev.
+o Computation of 2-sample Kolmogorov-Smirnov statistic in case of ties
+        was not correct.  Issue: MATH-1197.
 
 Changes:
-o Added Laguerre complex solve methods taking maxEval parameters.  Issue: MATH-1213. 
+o Modified 2-sample KolmogorovSmirnovTest to handle ties in sample data. By default,
+        ties are broken by adding random jitter to input data. Also added bootstrap method
+        analogous to ks.boot in R Matching package.  Issue: MATH-1246.
+o Added bootstrap method to KolmogorovSmirnov test.  Issue: MATH-1246.
+o Added constructors taking sample data as arguments to enumerated real and integer distributions.  Issue: MATH-1287.
+o Improved performance of sampling and inverse cumulative probability calculation
+        for geometric distributions.  Issue: MATH-1276.
+o Representation of Kolmogorov-Smirnov statistic as integral value.  Issue: MATH-1274.
+o Faster generation of Zipf distributed random numbers by using rejection-inversion sampling.  Issue: MATH-1220.
+o Improved performance of sort-in-place methods by avoiding boxing.  Issue: MATH-990.
+o Refactored implementation of the "miscrosphere projection"
+        interpolation algorithm.
+        New classes: "MicrosphereProjectionInterpolator",
+        "InterpolatingMicrosphere" and "InterpolatingMicrosphere2D"
+        replace "MicrosphereInterpolator" and "MicrosphereInterpolatingFunction".
+        (package "o.a.c.m.analysis.interpolation").  Issue: MATH-1243.
 
 
 Have fun!

http://git-wip-us.apache.org/repos/asf/commons-math/blob/9df79570/src/changes/changes.xml
----------------------------------------------------------------------
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 8b7a409..90e8dc9 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -50,7 +50,33 @@ If the output is not quite correct, check for invisible trailing spaces!
     <title>Commons Math Release Notes</title>
   </properties>
   <body>
-    <release version="3.6" date="XXXX-XX-XX" description="">
+    <release version="3.6" date="2016-01-04" description="
+This is a minor release: It combines bug fixes and new features.
+ Changes to existing features were made in a backwards-compatible
+ way such as to allow drop-in replacement of the v3.x JAR file.
+
+Most notable among the new features are:
+ field-based version of Ordinary Differential Equations framework,
+ numerous improvements in distributions, statistics and neuralnet packages,
+ refactored implementation of microsphere interpolation algorithm,
+ explicit specification of rotation convention to use (both vector
+ operator and frame transform conventions are now available).
+
+The minimum version of the Java platform required to compile and use
+ Commons Math is Java 5.
+
+Users are encouraged to upgrade to this version as this release not
+ only includes bug fixes but also deprecates numerous classes and
+ methods that will be deleted from the next major release (4.0).
+
+  Caveat:
+  1. The implementation of the BOBYQA optimization algorithm is in alpha
+  state (cf. MATH-621): Many code paths are untested, and we are looking
+  for volunteers to improve the code readability, robustness and performance
+  and to extend the unit tests suite.
+  2. A few methods in the FastMath class are in fact slower that their
+  counterpart in either Math or StrictMath (cf. MATH-740 and MATH-901).
+">
       <action dev="psteitz" type="fix" issue="MATH-1310">
         Improved performance and accuracy of 2-sample KolmogorovSmirnov tests.
       </action>