about RNG-127.]
Thanks,
Gilles
>> [...]
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
e. you have to "clone"
the repository into your projects' GH space and modify there).
Regards,
Gilles
[1] https://www.apache.org/foundation/how-it-works.html#roles
[2] The alternative is uploading patches to the
]
master-old [ y/n ]
modularized_master [ y/n ]
task-MATH-1366 [ y/n ]
?
Gilles
[1] This suggestion is a rehash of
https://markmail.org/message/wtuvaij74agbrm2l
[2] git push origin --delete branch_name
-
To unsubscribe,
Le ven. 6 août 2021 à 04:01, Matt Juntunen a écrit :
>
> Gilles,
>
> > I do _not_ ask any work to be done in order to complicate the release
> > process and/or review.
> > My question was (cf. above and the other thread) whether singling out
> > the "exampl
Hi.
Le jeu. 5 août 2021 à 18:01, Alex Herbert a écrit :
>
> On Thu, 5 Aug 2021 at 14:07, Gilles Sadowski wrote:
>
> > Le jeu. 5 août 2021 à 14:08, Gary Gregory a
> > écrit :
> > >
> > > I agree with Matt.
> >
> > Nobody seems to
ntioned release date ("2020-04-08") is also wrong.
Regards,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
e same way that
unit tests are, because they could sometimes exercise the code in a way
which the unit tests do not.
Maybe I misunderstood Matt's proposal, which I thought was was to not
release the examples (i.e. leaving them out of the release branch).
Regards,
Gilles
P.S. The issue of what
Le jeu. 5 août 2021 à 01:46, sebb a écrit :
>
> On Wed, 4 Aug 2021 at 13:38, Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Le mer. 4 août 2021 à 04:27, Matt Juntunen a
> > écrit :
> > >
> > > Hello,
> > >
> > > I apolo
Le mer. 4 août 2021 à 15:54, Gary Gregory a écrit :
>
> On Wed, Aug 4, 2021 at 9:27 AM Gilles Sadowski wrote:
> >
> > Hello.
> >
> > Shall we use "ASF" whenever such changes are made?
>
> I do not think so, the name of the Project is "Apache Com
Hello.
Shall we use "ASF" whenever such changes are made?
Regards,
Gilles
Le mer. 4 août 2021 à 15:06, a écrit :
>
> This is an automated email from the ASF dual-hosted git repository.
>
> aherbert pushed a commit to branch master
> in repository https://gitbox.apa
ublic API portions?
FTR, I quote the question raised in another thread where this issue
was first mentioned:
"[...] how can we release (some official version of) the project as source
without also releasing the (convenie
Le mar. 3 août 2021 à 00:09, Alex Herbert a écrit :
>
> The PoissonDistribution defines the method:
>
> /**
> * Calculates the Poisson distribution function using a normal
> * approximation. The {@code N(mean, sqrt(mean))} distribution is used
> * to approximate the Poisson distribution. The
n and standard
> deviation of the logarithm of the random variable X.
Just a name change?
+1
Gilles
>
> Alex
>
>
> [1] https://en.wikipedia.org/wiki/Log-normal_distribution
> [2] https://uk.mathworks.com/help/stats/prob.lognormaldistribution.html
> [3] https://stat.ethz.ch/R-man
Le lun. 2 août 2021 à 17:29, Gary Gregory a écrit :
>
> IMO make Java 8 the platform requirement.
+0.5 (if the cause is not obvious).
[I don't think that we'll get complaints from people running on Java 1.6
or 1.7 (?).]
Regards,
Gilles
>
> Gary
>
> On Mon, Aug 2, 2021,
ld be consistent with the official release material being
source code.]
Gilles
>
> Any opinions?
>
> Alex
>
> [1] https://maven.apache.org/docs/3.3.9/release-notes.html
> [2] https://maven.apache.org/guides/mini/guide-using-toolchains.html
--
> >
>
> That would be cleaner. The distribution is only used to allow the
> EmpiricalDistribution to function without knowing details of the bin, i.e.
> all bins have a kernel that is a distribution.
Done in commit 3df6d879e701b442fabf709c8143e6ca8f8f9547.
Gilles
> [...]
--
y.
> >
> > [1] https://issues.apache.org/jira/browse/MATH-984
> >
>
> Opinion on dropping ConstantContinuousDistribution
The class is used in Commons Math.[1]
> since the use case from
> Commons Math does not apply?
Do you mean that this ad-hoc class should be m
Le dim. 1 août 2021 à 19:57, Alex Herbert a écrit :
>
> On Sun, 1 Aug 2021 at 15:57, Gilles Sadowski wrote:
>
> >
> > >
> > > 1. Remove the method
> >
> > +1
>
>
> If we remove:
>
> ContinuousDistribution.probability(double)
>
>
uble v = value;
> if (Double.isNaN(v)) {
> value = v = computeValue();
> }
> return v;
> }
>
> This adds a lot of complexity to the classes.
>
> I would opt for option 1 in order to optimise the distribution in use and
> take the performanc
Hi.
Le dim. 1 août 2021 à 18:52, Alex Herbert a écrit :
>
> On Sun, 1 Aug 2021 at 15:57, Gilles Sadowski wrote:
>
> >
> >
> > Do you think that the API defined in the
> > "commons-statistics-distribution"
> > module is suitable for implemen
code being
exercised by that new tool. [I've no idea of how long is long enough.]
Then, as a matter of preference, I'd still suggest that "Commons RNG"
be released first (if the latter's next release is pending).
Best,
Gilles
> As before, the following modules would be included:
both continuous and discrete distributions. There is no
> additional probability function.
>
> Thus the method has no use in the current library. Here are two options:
>
> 1. Remove the method
+1
Thanks,
Gilles
> 2. Implement the method in the ConstantContinuousDistribution to
ct.
>
> We now have for all distributions:
>
> /** returns {@code P(X > x)} */
> double survivalProbability(int x)
>
> I suggest removing the upperCumulativeProbability method from
> the HypergeometricDistribution.
+1
Thanks,
Gilles
> It computes a different value (as it
t that a Commons component should depend on
a plotting library, it's likely "no go".
Would a GA implementation need this?
Again, if the purpose is to follow progress of the computation, we
should define appropriate interfaces to allow data collection in
real time. How those are processed (e.
to calculate population statistics if required.
You are certainly welcome to refactor the parts of the "o.a.c.m.stat"
package which would be of interest for that purpose.
Please note that redesign statistical functionalit
eptions being the only ones
checked. You could propose that FileNotFound or failures connecting
could be in that basket — but I/O failures reading or writing once the
file is open, are almost completely not.
---CUT---
Thanks,
Gilles
>
> -Matt
>
> On Sat, Jul 24, 2021 at 12:11 PM Gilles
ot;checked" vs "unchecked".
> As an end
> user of an application that uses this library, I want to know if the
> file I provided was just plain invalid versus if it just contained a
> wonky geometry.
I'm not sure I understand the issue (it seems to me that both are
irrecov
xception should be
accompanied by an example demonstrating what the library does in order
to _recover_. [If it doesn't to anything (other than throw, rethrow, or log an
error message) then an unchecked exception should be u
> constructor as deprecated. The public constructor creates a wrapper class
> around a delegate which implements sampling. Use of the factory constructor
> directly creates the optimal sampler. So use of the constructor should be
> avoided. Marking it as deprecated woul
Le jeu. 22 juil. 2021 à 01:05, Matt Juntunen
a écrit :
>
> Alex, you are correct that a large number of the SonarQube issues can
> be closed as "won't fix". I've opened INFRA-22130 [1] so I can get
> admin access to make those changes.
>
> Gilles, what do you
antee of BC.
Same for all the math-related components.
> >
> > Gary
> >
> > On Wed, Jul 21, 2021, 08:06 Gilles Sadowski wrote:
> >
> > > Hi.
> > >
> > > Le mer. 21 juil. 2021 à 05:09, Matt Juntunen
> > > a écrit :
> > > >
>
not release the "io" modules, or
* provide them as "examples" (although I guess that it would
not make a difference in the event of a security bug).
I'm not really pushing for either of the above two. Instead, we
we should try and clean up everything[1][2] before the first stab
eviewers).
> I have not looked at the commons-math examples, though.
Those that illustrate usage of the "neuralnet" codes are some kind of
validation tests; without them, unit tests are not sufficient to demonstrate
th
answer can be given...
>
> -Matt J
>
> On Sun, Jul 18, 2021 at 5:14 PM Gilles Sadowski wrote:
> >
> > > > > > [...]
> > > > > Building from the project root I get the same error you reported.
> > > > >
> > > > > This po
a release and it would just make more sense to make that one
first...
Gilles
>
> -Matt J
>
> On Tue, Jul 20, 2021 at 12:56 PM Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Le mar. 20 juil. 2021 à 04:01, Matt Juntunen
> > a écrit :
> > >
> > >
issue raised recently about what to do with the
"examples" code. Should it be part of the released artefacts?
Best,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
hey can be included as a
> dependency and that will bring everything upstream with it to a project.
>
> The question is whether the shaded jar has value as a released artifact. I
> always considered them proof-of-ap
Hi.
Le sam. 17 juil. 2021 à 18:17, Alex Herbert a écrit :
>
> On Sat, 17 Jul 2021 at 15:59, Alex Herbert wrote:
>
> >
> >
> > On Sat, 17 Jul 2021 at 14:17, Gilles Sadowski
> > wrote:
> >
> >> Hi.
> >>
>
en-shade-plugin:3.1.1:shade (default) on
project examples-sofm: Error creating shaded jar:
/home/gilles/devel/java/apache/commons-math/trunk/commons-math-neuralnet/target/classes
(Is a directory) -> [Help 1]
---CUT---
Any idea?
Thanks,
Gilles
>>> [...]
t;site"?
> The pom would have to be
> updated to bind the other plugins from the default goal to this phase with
> executions.
Is there something to be changed so [Math] is aligned with [RNG]?
Thanks,
Gilles
>
> Alex
>
>
> [1]
> https://maven.apache.org/guides/introduction/int
Le mer. 14 juil. 2021 à 12:10, sebb a écrit :
>
> On Wed, 14 Jul 2021 at 10:29, Gilles Sadowski wrote:
> >
> > Le mer. 14 juil. 2021 à 11:16, sebb a écrit :
> > >
> > > On Wed, 14 Jul 2021 at 10:03, Gilles Sadowski
> > > wrote:
>
Le mer. 14 juil. 2021 à 11:16, sebb a écrit :
>
> On Wed, 14 Jul 2021 at 10:03, Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Is it correct that
> > $ mvn site site:stage
> > and
> > $ mvn
> > behave differently (i.e. that the latter would
?
Thanks,
Gilles
Le mer. 14 juil. 2021 à 01:01, Alex Herbert a écrit :
>
> On Tue, 13 Jul 2021 at 23:41, wrote:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erans pushed a commit to branch master
> > in repository https://g
ly trust.
>
> All the best, and good work,
Thanks,
Gilles
> > [...]
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
ns require the components to be installed instead of
> packaged.
>
> mvn site
> Check the site reports in:
> - Windows: target\site\index.html
> - Linux: target/site/index.html
>
> 6) Build the site for a multi-module project
>
> mvn site
> mvn sit
Le sam. 10 juil. 2021 à 19:23, Gary Gregory a écrit :
>
> Since tags make sense to see what's been ADDED since 1.0.
Well, of course. IMHO even for the additions, the tags are next to useless in
Commons components.
Gilles
>
> On Sat, Jul 10, 2021, 13:20 Gilles Sadowski wrote:
>
Le sam. 10 juil. 2021 à 18:30, Matt Juntunen
a écrit :
>
> Do we want to add "@since" tags to Javadocs?
I don't think that they add much.
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.or
of arrays.
I don't also know whether the warning (I didn't notice it) is a problem, but
if it is, I'd rather remove the "implements" clause than the method. [I don't
have a real-life example for using the interface.]
Regards,
Gilles
-
t;commons-numbers-arrays" should go in.
Regards,
Gilles
>
> -Matt J
>
> On Tue, Jul 6, 2021 at 5:17 PM Matt Juntunen
> wrote:
>
> > Hello,
> >
> > Are we ready for a 1.0 release of commons-numbers? Any pe
> [...]
> > One is "sorry, this is an invalid archive" while the other is "something
> > > went wrong reading the archive - printStackTrace". If that distinction is
> > > not important to you - so be it. To me that's a big difference.
> >
> > Never said such a thing.
> >
>
> Not sure what "thing"
the caller from himself (by throwing *any*
exception rather than crashing the JVM or giving root access. ;-)
> For me "recoverable" does not mean running the same code with the same
> input twice and expecting a different result.
In effect this is exactly what one does in the only
le", the second condition also fails (but YMMV):
If the library throws an exception because it cannot make sense of the archive,
the caller still has no clue how to recover (except trying again by
assuming that
the error will automagically fix itself).
Gilles
[1] Copied from
https://ahdak.
Le mer. 30 juin 2021 à 11:55, PeterLee a écrit :
>
> > (1) catch all RuntimeExceptions, wrap them in an IOException (possibly a
> >subclass) and throw the IOException
>
> -1
>
> I agree with sebb about this option - this may accidentally convert a bug
> into
> something else.
>
> > (2) catch
catch
all exceptions at some point.
The distinction between checked and unchecked is related to the
question of "recoverable or not", not about "handling or not".
> if you don’t care you have to handl
Le mar. 29 juin 2021 à 22:24, Stefan Bodewig a écrit :
>
> Hi
>
> I'm sorry, but I'm unable to see what would or would not work for the
> people who chimed in. Short of calling for a vote, lets try with a poll
> that could show whether there is some sort of solution that is
> acceptable to
Le lun. 28 juin 2021 à 08:52, Stefan Bodewig a écrit :
>
> On 2021-06-27, Gilles Sadowski wrote:
>
> > Le dim. 27 juin 2021 à 21:15, Stefan Bodewig a écrit :
>
> >> As I said, we can as well document that each method could throw
> >> arbitrary RuntimeExcepti
Le dim. 27 juin 2021 à 21:15, Stefan Bodewig a écrit :
>
> On 2021-06-27, Gilles Sadowski wrote:
>
> > Hi.
>
> >> [...]
>
> >> it seemed Gilles was opposed to this idea
>
> > Rather (IIRC) my last comment was that it was your choice as to
> &
Le dim. 27 juin 2021 à 19:05, Torsten Curdt a écrit :
>> [...]
> > > I'd argue that signaling this problem should be a checked exception.
> > > IMO this provides a clearer contract to the user.
> >
> > It doesn't. The user would have a false sense of security believing so.
> >
>
> I guess I
the input is wrong, we should (IMO)
throw an IAE; hence it is indeed inconsistent that depending on
how/when the error is discovered, the exception would be different.
But as said previously, it could boil down to a choice of API.
Regards,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Hi.
> [...]
> it seemed Gilles was opposed to this idea
Rather (IIRC) my last comment was that it was your choice as to
what the API should look like.
My opinion on the matter was along Gary's lines (which is J. Bloch's
rationale provided in "Effective Java").
Indeed I persona
thCache()" on an existing instance), the "saved" copying time will
be marginal wrt the lost time due to repeating the other (likely much
lengthier) computations.
Regards,
Gilles
[1] Through JMH benchmarks _on the use-case at hand_.
Le dim. 20 juin 2021 à 09:35, GitBox a écrit :
&
Hi.
Le mar. 15 juin 2021 à 13:25, Erik Svensson a écrit :
>
>
>
> On 2021-06-08, 13:29, "Gilles Sadowski" wrote:
>
> Hello.
>
> Le mar. 8 juin 2021 à 10:30, Erik Svensson a
> écrit :
> >
> > (sent prev to the wro
at you mean. If it's about the possiblity
to use JPMS: "Commons RNG" project has an example[1] showing that it
seems to work when the code is used within a Java 9+ environment, even
though the component itself is still targetted at Java 1.6.
Regards,
Gilles
[1]
https://gitbox.apache.
ies provided in [Math] v3.6.1 whose
target was Java 5 (!).
A few years ago, the bump to Java 8 was considered a bold move
(for "Commons"). :-}
If we are sure that Java 11 is no problem for anyone who'd go
through the upgrade effort, then indeed why not?
Gilles
> As Java 17 starting
Le jeu. 10 juin 2021 à 13:05, sebb a écrit :
>
> Thanks.
>
> I've updated the RELEASE-NOTES accordingly (feel free to tweak the text)
AFAIK, this is an auto-generated file (from changes.xml).
Gilles
>
> On Thu, 10 Jun 2021 at 00:58, Alex Herbert wrote:
> >
> >
; > >
> > > > Have you tried "9" instead of "1.9"?
> > > >
> > >
> > > I've corrected that in the pom, thanks.
> > >
> > > I think the issue is that Gilles used JDK 8 to try and build it. You can
> > > run using the project's ma
l networks module due to a
> case statement fall through. This is intentional so I added an exclusion. I
> then get failures later on and have not fixed them all.
The default build now stops at two SpotBugs issues in "AccurateMath";
they relate to two magic numbers that are close to pi
Le mer. 9 juin 2021 à 16:10, Alex Herbert a écrit :
>
> On Wed, 9 Jun 2021 at 15:02, Gilles Sadowski wrote:
>
> > Le mer. 9 juin 2021 à 15:58, Alex Herbert a
> > écrit :
> > >
> > I'm doing it...
> >
>
> OK. I was trying to fix the math
ompiler-plugin:3.8.1:testCompile
(default-testCompile) on project commons-numbers-core: Fatal error
compiling: invalid target release: 1.9 -> [Help 1]
---CUT---
Regards,
Gilles
-
To unsubscribe, e-mail: dev-unsubsc
Le mer. 9 juin 2021 à 15:58, Alex Herbert a écrit :
>
> On Wed, 9 Jun 2021 at 14:55, Gilles Sadowski wrote:
>
> > Hello.
> >
> > Le mer. 9 juin 2021 à 15:49, Erik Svensson a
> > écrit :
> > >
> > > Hi!
> > >
> > >
>
the inconvenience.
This part of the "Commons Numbers" API has been undergoing
changes in the last 12 hours.
> or should I do something?
No. Hopefully it'll soon come back to normal.
This glitch will probably reoccur with
https://
ed also for 3.x ?
>
> - What should I fork of? Is it still modularized_master?
>
> - Should FastMath be renamed AccurateMath?
>
I've answered on JIRA:
https://issues.apache.org/jira/browse/MATH-1591
Hello Samy.
Le lun. 7 juin 2021 à 11:51, Samy Badjoudj a écrit :
>
> Hello Gilles,
>
> Is there something we need to change
> https://github.com/apache/commons-math/pull/190, that one comes after
> the discussion we had.
I probably failed to convey it but the main point
Hello.
Le lun. 7 juin 2021 à 06:51, Stefan Bodewig a écrit :
>
> On 2021-06-06, Gilles Sadowski wrote:
>
> > Le dim. 6 juin 2021 à 07:51, Stefan Bodewig a écrit :
>
> >> Hi
>
> >> I'm thinking about a specific IOException subclass that is thrown when a
&g
Le lun. 7 juin 2021 à 00:03, Ralph Goers a écrit :
>
>
>
> > On Jun 6, 2021, at 11:44 AM, Gilles Sadowski wrote:
> >
> > Le dim. 6 juin 2021 à 14:54, Gary Gregory a écrit :
> >>
> >> Here is the draft I plan on submitting:
> >>
&
tion must restricted to signalling
a problem that can be recovered from.
The situation described here is that the library doesn't even know
what the problem is.
Gilles
>
> On Sun, 6 Jun 2021 at 12:01, Gilles Sadowski wrote:
> >
> > Le dim. 6 juin 2021 à 07:51, Stefan Bodewi
"No new committers"
In the past, there was some (informal, ill-defined)
demonstration of interest through sustained activity
that led to being proposed commit access (through
which most of the activity was performed).
Hence the question: Given that there are indeed many
contributions th
ticularly "healthy".
And, again, the advertised numbers of committers and PMC members
could be formally correct but is, for any purpose, misleading.
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
part of the story as to what is the original problem.
>
> https://github.com/apache/commons-compress/compare/catch-RuntimeExceptions
>
> is this a good idea?
IMO, no.
Why would one want to create a checked exception from
an unchecked one?
> Should anything be worded/named differently?
Illeg
Le sam. 5 juin 2021 à 15:34, Gilles Sadowski a écrit :
>
> Hello.
>
> Towards releasing CM 4.0, I've postponed many reports to
> "later" (version "4.X").
> Help is welcome to review those that remain targeted at the
> upcoming version.[1]
Please
Hello.
Towards releasing CM 4.0, I've postponed many reports to
"later" (version "4.X").
Help is welcome to review those that remain targeted at the
upcoming version.[1]
Regards,
Gilles
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MATH%20AND%20fixVersi
see them, why not exclude them in your local
> clone (.git/config)?
> Like so:
> https://stackoverflow.com/a/37165609/1549977
I don't think that non-users having to work around is the proper
solution.
Thanks,
Gilles
>
>
>
> Am Fr., 4. Juni 2021 um 19:20 Uhr schrieb Gilles Sadows
There must be, since we don't see all the other PRs.
> If you are not a committer, you can safely ignore them.
Well, I'd like to know how to achieve that.
For example, doing
$ git branch -a
there are about "dependabot" lines that clutter the output.
Regards,
Gilles
>
> You p
listed here:
https://gitbox.apache.org/repos/asf?p=commons-geometry.git
>
> You can disable the bot using a config file or exclude some dependencies
> etc.
Indeed, is this intended or is there a misconfiguration somewhere?
Gilles
>
> Most projects use it by now, but often major up
Hello.
What's the purpose of all those "dependabot" branches?
$ git branch -a
1.0-beta1-release
* master
remotes/github/master
remotes/origin/1.0-beta1-release
remotes/origin/GEOMETRY-53
remotes/origin/GEOMETRY-54
remotes/origin/GEOMETRY-56
ntations, none of which
> have additional fields to include in the hash.
Done.
Thanks,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Le mar. 1 juin 2021 à 15:25, Samy Badjoudj a écrit :
>
> Thanks Gilles, please find below my remarks
>
>
> On 01.06.21 12:37, Gilles Sadowski wrote:
> > Le lun. 31 mai 2021 à 02:07, Gilles Sadowski a écrit
> > :
> >> Hello.
> >>
> >
Hi.
Le mar. 1 juin 2021 à 07:28, Samy Badjoudj a écrit :
>
> Hi Gilles,
>
> Following up the discussion on
> https://issues.apache.org/jira/browse/MATH-1597
>
> * My suggestion was for "skip" to be similar to "jump" (i.e. it would
> return a "Skip
Le lun. 31 mai 2021 à 02:07, Gilles Sadowski a écrit :
>
> Hello.
>
> Halton and Sobol sequences have been implemented in the "random"
> package. From Wikipedia[1]:
> ---CUT---
> Low-discrepancy sequences are also called quasirandom sequences,
> due to
d go in module "commons-math-legacy-core"
(where "FastMath" was moved and renamed "AccurateMath").
Note that the "legacy" specifier refers to codes that depend on other
legacy codes ("legacy-core" still depends on "legacy-exception&qu
er is used to denote more clearly
that the values of a low-discrepancy sequence are neither random nor
pseudorandom.
---CUT---
TL;DR;
I propose to create an interface "LowDiscrepancySequence" to properly
represents the concept (as opposed to "RandomVectorGenerator").
Regards,
G
-parent: You're not authorized to
run analysis. Please contact the project administrator. -> [Help 1]
---CUT---
Any clue?
Gilles
[1]
https://ci-builds.apache.org/job/Commons/job/commons-math%20(SonarQube)/6/cons
Le dim. 30 mai 2021 à 00:57, sebb a écrit :
>
> On Sat, 29 May 2021 at 21:21, Gilles Sadowski wrote:
> >
> > Le sam. 29 mai 2021 à 16:42, sebb a écrit :
> > >
> > > What's wrong with the Subject?
> >
> > "[commons-numbers]"
> >
&g
Le sam. 29 mai 2021 à 16:42, sebb a écrit :
>
> What's wrong with the Subject?
"[commons-numbers]"
Commit was to "commons-statistics" repository.
>
> Looks OK to me.
>
> On Sat, 29 May 2021 at 15:17, Gilles Sadowski wrote:
> >
> &
The (auto-generated) "Subject: " line is wrong.
Is it something that we can fix, or should I report to INFRA?
Gilles
Le sam. 29 mai 2021 à 15:46, a écrit :
>
> This is an automated email from the ASF dual-hosted git repository.
>
> erans pushed a commit to branch master
Le ven. 28 mai 2021 à 19:32, Gilles Sadowski a écrit :
>
> Le jeu. 27 mai 2021 à 18:06, Samy Badjoudj a écrit :
> >
> > Hi,
> >
> > Following up on modularization of apache commons maths.
> >
> > https://issues.apache.org/jira/browse/MATH-1586 with
>
ster" branch.
>
> I moved the classes from org.apache.commons.math4.legacy.util to
> packages where they are used exclusively (stat,linear).
As a follow-up, I've opened
https://issues.apache.org/jira/browse/MATH-1592
Regards,
Gilles
>
> Should ease the split of legacy sub m
IMO it is a [Text] feature (hence the prefix added to the "Subject: " line).
Regards,
Gilles
Le ven. 28 mai 2021 à 08:21, Miguel Munoz
a écrit :
>
> Here's one take on the problem:
> /**
> * Created by IntelliJ IDEA.
> * Date: 2/4/21
> * Time: 1:36 AM
> *
Le jeu. 27 mai 2021 à 13:53, Erik Svensson a écrit :
>
>
>
> On 2021-05-27, 11:59, "Gilles Sadowski" wrote:
>
> WARNING - External email; exercise caution.
>
> Hi.
>
> Le jeu. 27 mai 2021 à 11:32, Erik Svensson
also an opportunity to hide
functionality that should not be part of the public API (i.e. make the
corresponding classes private or package-private).
This thread is dedicated to listing the pending changes.
Regards,
Gilles
[1] https://markmail.org/message/65654d2qvcayqyfk
[2] To be merged into &qu
401 - 500 of 4251 matches
Mail list logo
