Re: [Numbers] Where do we stand?

2018-01-26 Thread Eric Barnhill
First of all, AFAICT, none of the issues I worked on have ever been marked "resolved". I don't believe I have the power to mark them this way myself. Eric On Fri, Jan 26, 2018 at 1:49 AM, Gilles wrote: > Hello. > > JIRA lists 12 unresolved issues for the v1.0 target. > > After quite a lot of ni

Re: [Numbers] Where do we stand?

2018-01-26 Thread Gilles
Hi Eric. On Fri, 26 Jan 2018 11:29:50 +0100, Eric Barnhill wrote: First of all, AFAICT, none of the issues I worked on have ever been marked "resolved". As a matter of principle, no issue can be "resolved" if it would imply a code change and said change was not merged into the "master" branch

[RNG] Towards v1.1

2018-01-26 Thread Gilles
Hello. I propose to release the next version of "Commons RNG". The web site with the current (today) development version (to become 1.1) is on-line: http://commons.apache.org/rng Could someone please take on the following issue (JDK 9): https://issues.apache.org/jira/browse/RNG-40 and fix it

[Numbers] Jenkins build failure

2018-01-26 Thread Gilles
Hi Eric. Your recent merge contains Javadoc errors that make Java 8 unhappy: https://builds.apache.org/view/A-D/view/Commons/job/commons-numbers/62/console Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.

Re: [Numbers] Jenkins build failure

2018-01-26 Thread Eric Barnhill
ok will fix On Fri, Jan 26, 2018 at 4:23 PM, Gilles wrote: > Hi Eric. > > Your recent merge contains Javadoc errors that make Java 8 > unhappy: > https://builds.apache.org/view/A-D/view/Commons/job/commons- > numbers/62/console > > Regards, > Gilles > > > --