Hello.
Le mer. 14 oct. 2020 à 21:41, John Patrick a écrit :
>
> before i waste time looking at upgrading tests...
>
> any objections if i upgrade tests to use assertAll and assertThrows
> introduced in JUnit jupiter?
>
> I see it as less tech debt removal and I'm happy to spend time doing
> the
t;) branch?
[I recall that there have been other suggestions towards improving
the API of the "autodiff" implementation.]
There are many identified issues still to be fixed in CM, but that
shouldn't prevent us from releasing a "4.0-beta" version.
Best regards,
Gilles
[1] https://issues
Hello.
2020-09-17 21:47 UTC+02:00, Oliver Heger :
> Hi all,
>
> once we had a discussion (it must be one or two years ago) whether
> Commons could support components in other (JVM) languages, too. IIRC,
> there were no strong objections, but there has never been a follow up.
>
> For a project in
Le mer. 16 sept. 2020 à 21:09, Gary Gregory a écrit :
>
> I think we really want the PRs, the main benefit is to have the software
> built and tested WITH the dependency update, that is a huge time saver.
Yes, but the bot should submit the PR only when asked by a human,
at times where it brings
Le mer. 16 sept. 2020 à 14:42, Jochen Wiedmann
a écrit :
>
> On Wed, Sep 16, 2020 at 2:38 PM Gilles Sadowski wrote:
>
> > Isn't what
> >https://spamassassin.apache.org/
> > is about?
>
> Not that I am uptodate, but at least historically it hasn't. It's
>
Le mer. 16 sept. 2020 à 14:29, Jochen Wiedmann
a écrit :
>
> On Wed, Sep 16, 2020 at 12:37 PM Gilles Sadowski wrote:
>
> > As I've already stated in the previous "discussion" (from
> > where I was left with the only solution of filtering out), a lot
> > of th
2020-09-16 8:16 UTC+02:00, Jochen Wiedmann :
> On Mon, Sep 14, 2020 at 2:48 PM Gary Gregory
> wrote:
>
>> [...]
>> I don't really care about
>> the emails one way or another.
Then why force them down onto people who did care?
>
> I don't need a compromise. Just wanted to trigger a discussion.
Le lun. 14 sept. 2020 à 14:48, Gary Gregory a écrit :
>
> [...]
> - Jochen: What you do with your inbox is your business ;-) What is
> the happy compromise here? Do you want a separate email list? Zero
> Dependabot emails anywhere? If you feel strongly about this, please
> create a [POLL] thread
Hello.
2020-09-10 4:53 UTC+02:00, Peter Lee :
>> The builds.apache.org CI builds did that if they were set up to do so.
>>
>
> Is this implemented by a mvn deploy or some other ways(a jenkins plugins or
> some other things)?
"Goals and options" item in the "Build" section of the "Configure"
menu
Hello.
> > [...]
> > see an explanation for why it is necessary
> > (or even helpful) to include artefact hashes in the vote mail.
> >
> I agree and understand all your points here.
Well, I don't.
An explanation would be useful indeed.
> > Validating the svn revision for the dist repo [ ... vs
Le jeu. 3 sept. 2020 à 17:01, Gary Gregory a écrit :
>
> On Thu, Sep 3, 2020 at 10:47 AM Gilles Sadowski
> wrote:
>
> > Le jeu. 3 sept. 2020 à 14:49, Gary Gregory a
> > écrit :
> > >
> > > Over on GH [1], Matt mentions retry APIs like retry4j w
Le jeu. 3 sept. 2020 à 14:49, Gary Gregory a écrit :
>
> Over on GH [1], Matt mentions retry APIs like retry4j which is a concept we
> could reuse in Commons components like IO, Lang, Pool (and by extension
> DBCP).
>
> While this might initially feel like a fit for Lang, I wonder what the
>
Le jeu. 3 sept. 2020 à 13:55, sebb a écrit :
>
> On Wed, 2 Sep 2020 at 20:54, Gary Gregory wrote:
> >
> > On Wed, Sep 2, 2020, 15:50 Xeno Amess wrote:
> >
> > > Why so hurry?
> > >
> >
> > I need to use new APIs now. Releases happen all the time, more releases
> > more often is better than big
2020-09-01 19:08 UTC+02:00, Alex Herbert :
> In addition I should have said sorry and next time I will wait longer. I
> appreciate there are a lot of servers and maybe I got lucky with the ones I
> was watching for replication.
No need to apologize: We don't have to inspect all the slow
Le jeu. 27 août 2020 à 13:22, Gilles Sadowski a écrit :
>
> Le jeu. 27 août 2020 à 10:06, Mark Thomas a écrit :
> >
> > On 27/08/2020 00:21, Gilles Sadowski wrote:
> > > Hi.
> > >
> > > Something happening recently (apparently unrelated to changes
&
Le jeu. 27 août 2020 à 10:06, Mark Thomas a écrit :
>
> On 27/08/2020 00:21, Gilles Sadowski wrote:
> > Hi.
> >
> > Something happening recently (apparently unrelated to changes
> > in the repository):
> > https://ci-builds.apache.org/job/Commons/job/comm
Hi.
Something happening recently (apparently unrelated to changes
in the repository):
https://ci-builds.apache.org/job/Commons/job/commons-statistics/3/console
https://ci-builds.apache.org/job/Commons/job/commons-numbers/2/console
2020-08-22 16:02 UTC+02:00, Gary Gregory :
> Here is a first cut:
>
> https://github.com/apache/commons-io/security/policy
And here is my suggestion:
https://github.com/apache/commons-rng/security/policy
YMMV,
Gilles
> [...]
rst class citizen in how we put a face on the project.
How does duplicate information improves anything
(marketing or otherwise)?
Ultimately, reports still have to be posted to an ASF-hosted
ML, and not on GH.
Gilles
>
> Gary
>
> On Sat, Aug 22, 2020, 10:15 Gilles Sadowski wrot
Hi.
2020-08-22 15:26 UTC+02:00, Gary Gregory :
> Hi All,
>
> You may have noticed (or nor) that GitHub has a Security [1] tab for our
> repositories. On this tab, you can define a Security Policy.[2] in a
> SECURITY.md (just like we have a README.md).
>
> I would like to fill this in with the
Le jeu. 20 août 2020 à 23:15, sebb a écrit :
>
> On Thu, 20 Aug 2020 at 21:54, Gilles Sadowski wrote:
> >
> > Le jeu. 20 août 2020 à 22:00, sebb a écrit :
> > >
> > > AFAICT the release artifacts have only sha512 files.
> > >
> > > However t
.
>
> Anyway the release distribution page [1] does not relate to Maven
> releases AFAIK.
OK.
Then, I'd suggest that we don't bloat the vote message with
files that don't matter.
Gilles
>
> On Thu, 20 Aug 2020 at 18:39, Gary Gregory wrote:
> >
> > On Thu, Aug 20, 2020
Hi Thomas.
Le jeu. 20 août 2020 à 09:14, Thomas Vandahl a écrit :
>
> Could I please ask for one more PMC vote?
IIUC[1], this release should not ship with SHA1 or MD5 files.
Regards,
Gilles
[1] https://infra.apache.org/release-distribution.html#sigs-and-sums
>
> TIA
> Bye, Thomas
>
> On
Hello.
Le jeu. 20 août 2020 à 13:56, Peter Lee a écrit :
>
> Hi all,
>
> The builds in jenkins and github actions are failing.
> For jenkins, the java7, 14 and 16 builds are failing. As we have moved from
> JAVA 7 to 8, maybe we should disable java 7 build in jenkins?
+1
Gilles
> Besides the
maven wrapper versions like the old style
> jenkins slave.
Thanks for the explanations.
The [Math] component could be used as guinea pig.
Best regards,
Gilles
>
> John
>
> On Wed, 19 Aug 2020 at 22:23, Gilles Sadowski wrote:
> >
> > Le mer. 19 août 2020 à 22:49, Gary Gregory a
Le mer. 19 août 2020 à 22:49, Gary Gregory a écrit :
>
> The consensus is do nothing IMO.
"Those who do the work" etc. (see below).
>
> What I really dislike is that if I have 20 components that over time end up
> containing 20 different versions of these Cmd/Sh/JavaSource/PropertiesFiles
>
atic builds),
we don't really care whether it is provided by "Vendor A" or
"Vendor B".
If the Travis service is redundant, is there any willingness to
cut the cost by using an equivalent GitHub service?
Will if reduce spending if we stop using Travis?
Gilles
> On Sat, 15 Au
2020-08-15 22:51 UTC+02:00, Geoffrey Blake :
> Not familiar with Apache CI, but github actions do not support Arm builds.
> Arm should be recognized as a first class build target these days. Travis
> allows Arm builds so not sure about the reasoning for moving off.
Also, is Travis computing time
Hello.
Le sam. 15 août 2020 à 19:22, Rob Tompkins a écrit :
>
> Hello all,
>
> I first want to thank John for bringing these points to light as I think we
> can have quite a healthy discussion about the CI/CD philosophy employed by
> the project (Apache Commons) generally. Furthermore, I hope
Hi.
Le sam. 15 août 2020 à 00:02, John Patrick a écrit :
>
> I've just noticed a load of pull requests that have been auto created
> by dependabot, for changes to be merged into my forked version of
> master.
>
> For commons-lang I've 20 PR's, commons-logging 10 PR's, I've not
> checked all the
Hello.
It seems that the migration script could not copy over all the
necessary information:
---CUT---
[ERROR] Failed to execute goal
org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar
(default-cli) on project commons-rng-parent: Not authorized. Please
check the properties
Le ven. 14 août 2020 à 17:34, Gilles Sadowski a écrit :
>
> Le ven. 14 août 2020 à 17:05, Alex Herbert a écrit
> :
> >
> > On Fri, 14 Aug 2020 at 15:40, Gilles Sadowski wrote:
> >
> > > Hi Alex.
> > >
> > > Le ven. 14 août 2020 à 16:07, Al
Le ven. 14 août 2020 à 17:05, Alex Herbert a écrit :
>
> On Fri, 14 Aug 2020 at 15:40, Gilles Sadowski wrote:
>
> > Hi Alex.
> >
> > Le ven. 14 août 2020 à 16:07, Alex Herbert a
> > écrit :
> > >
> > > On Fri, 14 Aug 2020 at 13:55, Gary G
Hi Alex.
Le ven. 14 août 2020 à 16:07, Alex Herbert a écrit :
>
> On Fri, 14 Aug 2020 at 13:55, Gary Gregory wrote:
>
> > This below is from the build list. If anyone wants to look over at
> > migration or recreating these builds, feel free to dig in.
> >
>
> I will have a look at moving the
Hello.
Le ven. 14 août 2020 à 14:55, Gary Gregory a écrit :
>
> This below is from the build list. If anyone wants to look over at
> migration or recreating these builds, feel free to dig in.
Thanks for the heads-up.
[I had no idea of the deadline; did INFRA send that information
to the
Le dim. 2 août 2020 à 15:37, Rob Tompkins a écrit :
>
>
>
> > On Aug 2, 2020, at 9:32 AM, Gilles Sadowski wrote:
> >
> > Le dim. 2 août 2020 à 15:13, Gary Gregory a écrit
> > :
> >>
> >> -1: I do not think we should release when a tes
Le dim. 2 août 2020 à 15:13, Gary Gregory a écrit :
>
> -1: I do not think we should release when a test breaks on Java 11, an LTS
> version; see below.
If everybody agrees, doesn't this become a Commons' *rule*
that could be taken off the RM's shoulders?
I mean, by setting up appropriate
Hi.
Thanks for detailing your POV. However...
Le dim. 26 juil. 2020 à 19:08, Melloware a écrit :
>
> I know there seems to to be a holy war
"holy war" certainly not.
The notion of "independence" would be appropriate.
> about the use of GitHub going on
> here but I thought I would just chime
Le dim. 26 juil. 2020 à 19:58, Rob Tompkins a écrit :
>
> I haven’t read all that’s going on here. But in my mind we treat GitHub as a
> first class citizen, right?
Depends on what that means.
As Matt said, it's our PR manager.
> We’re trying quite hard intact to make it our main working repo
Hello.
Le dim. 26 juil. 2020 à 19:04, Xeno Amess a écrit :
>
> I thought it was obvious so I didn't do the benchmark.
Performance is so *not* obvious that JMH prints a warning in its
output. [So even if the numbers don't match your expectation,
you might be right anyway, in some use-cases, or
ecated codes...
> Means maintaining such a branch for several months seems not quite worthy.
>
>> and look for further code bloat that could be removed from the next major
> release
>
> I will if I see any.
>
>
> Gilles Sadowski 于2020年7月26日周日 下午11:13写道：
>
>&
Hi Xeno.
2020-07-26 13:10 UTC+02:00, Xeno Amess :
>>> For examples about my prs at commons-lang,if my memory is correct, only
>>> gary (and sometimes kinow) reviewed my prs, and I don't think we have
> only
>>> two committers in commons-lang.
>
>> Are there JIRA reports?
>
> My log here is:
>
>
2020-07-26 5:00 UTC+02:00, Xeno Amess :
>>GitHub is basically our interactive pull request interface. If we didn’t
> have that, I bet we’d be running GitLab ourselves or similar.
>
> Yes, that is what I think gitbox lacks.
As Matt says above, the functionality is there. As noted in my
previous
Hi.
2020-07-25 21:03 UTC+02:00, Alex Herbert :
>
>
>> On 25 Jul 2020, at 19:25, Gilles Sadowski wrote:
>>
>> Hello.
>>
>> In the thread[1] from which the below quote is extracted:
>>> Would you be willing to provide a PR that deprecates the relevan
Hello.
In the thread[1] from which the below quote is extracted:
> Would you be willing to provide a PR that deprecates the relevant APIs and
> points to their equivalent in RNG? It will be more cruft we can trim for
> 4.0, whenever that happens.
Gary mentions that copy/paste is a "coding
Hello.
Le ven. 24 juil. 2020 à 17:45, Stefan Bodewig a écrit :
>
> This is an attempt at answering something raised be Gilles in a
> different thread. I'm afraid it is getting longer than I
> intended. Something seems to need to get out. Sorry.
>
> On 2020-07-23, Gilles Sadow
Le ven. 24 juil. 2020 à 17:39, Gary Gregory a écrit :
>
> On Fri, Jul 24, 2020 at 11:30 AM Rob Tompkins wrote:
>
> >
> >
> > > On Jul 24, 2020, at 9:41 AM, Torsten Curdt wrote:
> > >
> > >>
> > >> You can imagine all manner of jar-hell created by shading. For
> > instance:
> > >>
> > > -
Le ven. 24 juil. 2020 à 17:46, Matt Sicker a écrit :
>
> Shading also violates a lot of common ClassLoader assumptions like not
> having multiple copies of the same class in the same visible context (even
> if different packages)
How classes in different packages could be the same class?
Gilles
Hello.
Le ven. 24 juil. 2020 à 14:48, Gary Gregory a écrit :
>
> On Fri, Jul 24, 2020 at 6:03 AM Gilles Sadowski
> wrote:
>
> > 2020-07-24 11:25 UTC+02:00, Torsten Curdt :
> > > It still needs a person to decide to merge a PR for a new version.
> > > So this
Hi.
2020-07-23 15:59 UTC+02:00, Matt Sicker :
> [...] make every Commons component
> easily buildable in Jenkins [...]
How to do it practically?
Can we create a text file and drop it somewhere, or has
the configuration to be done in GUI ?
Gilles
2020-07-24 11:25 UTC+02:00, Torsten Curdt :
> It still needs a person to decide to merge a PR for a new version.
> So this indeed is just about the dependency upgrade policies.
>
> But isn't that what the version definition is for?
Ideally.
In practice, I think that all we can assume is that the
Hi Stefan and all.
2020-07-24 8:35 UTC+02:00, Stefan Bodewig :
> On 2020-07-24, Rob Tompkins wrote:
>
>>> On Jul 23, 2020, at 10:16 PM, Matt Sicker wrote:
>
>>> Also, how different is a bot proposing a dependency update from a human
>>> doing the same? The bot includes far more context about
Hello.
Le jeu. 23 juil. 2020 à 13:21, Olivier Lamy a écrit :
>
> On Thu, 23 Jul 2020 at 20:57, Gilles Sadowski wrote:
>
> > Hi.
> >
> > 2020-07-23 12:38 UTC+02:00, Olivier Lamy :
> > > Hi
> > > As you know the current Jenkins infra is migrating to
Hi.
2020-07-23 8:23 UTC+02:00, Stefan Bodewig :
> On 2020-07-23, Gilles Sadowski wrote:
>
>> If I'm not mistaken, the issues@ ML was intended to keep one
>> posted of and reactive on a human discussion happening on
>> JIRA. With the advent of JIRA-GitHub integrati
Hi.
2020-07-23 12:38 UTC+02:00, Olivier Lamy :
> Hi
> As you know the current Jenkins infra is migrating to another CI server.
> The current commons-* builds in the old Jenkins infra have been created
> manually and this will be a pain to transfer to the new one and to keep
> maintaining
for sure would give preference
to tools controlled by the Apache infrastructure
team.
Gilles
>
> On Wed, Jul 22, 2020 at 22:00 Gilles Sadowski wrote:
>
>> 2020-07-23 3:35 UTC+02:00, Torsten Curdt :
>> >>
>> >> > I realize that a local build seems to be
Hi.
As per the MLs definitions[1], "issues@" is
---CUT---
Only for e-mails automatically generated by the issue tracking system.
---CUT---
while "notifications@" is
---CUT---
For site staging build e-mails automatically generated by Buildbot.
---CUT---
Shouldn't this be made consistent one way
2020-07-23 3:35 UTC+02:00, Torsten Curdt :
>>
>> > I realize that a local build seems to be your gold standard.
>>
>> Not mine. "Commons".
>>
>
> You are arguing for it.
No I'm not. It (i.e "maven", "svn" then "git") was there
when I came here.
It could change but that's another discussion that
2020-07-23 3:09 UTC+02:00, Torsten Curdt :
>>
>>
>> > TBH not in terms of your "you act, and I must react" argument.
>>
>> It was not an argument, but a statement of fact.
>>
>
> Well, it "must react" feels a bit loaded.
Perhaps another (?) misunderstanding here.
The action came before the
2020-07-23 2:05 UTC+02:00, Rob Tompkins :
> -0.5 (real close to -1). Automated emails to commits@ is just part of being
> part of the project. Right?
I don't understand. What's the question?
Restating:
* "commit@" (a separate ML) is fine
* "issues@" combines redundant messages (i.e. zero
2020-07-23 1:22 UTC+02:00, Torsten Curdt :
>>
>> > It does not mean that a source distribution goes away.
>>
>> Nor did I mean that it would.
>> I commented on the remark that one's own computer
>> supposedly did not matter.
>>
>
> Ah, then it was only the "(that one does not really count.)" that
2020-07-23 1:37 UTC+02:00, Torsten Curdt :
> On Thu, Jul 23, 2020 at 12:51 AM Gilles Sadowski
> wrote:
>
>> 2020-07-23 0:14 UTC+02:00, Torsten Curdt :
>> >>
>> >> You act, and I must react?
>> >> Do I really have to spell it in even more words
gt;
> If anything, it might be clearer to rename issues@ to botsink@ or some
> such.
We should have both.
Gilles
>
> Gary
>
> On Wed, Jul 22, 2020 at 6:27 PM Gilles Sadowski
> wrote:
>
>> Hello.
>>
>> The situation with tool generated messages sent to
>
2020-07-23 0:14 UTC+02:00, Torsten Curdt :
>>
>> You act, and I must react?
>> Do I really have to spell it in even more words than
>> above?
>>
>
> You just sent me a message I didn't want - and I need to delete it now ;)
>
> But tongue in cheek aside. We are on a dev list.
> Commits, issues all
2020-07-23 0:07 UTC+02:00, Torsten Curdt :
>>
>> I don't agree: a source distribution assumes that one's own
>> computing resources is essential.
>> This project never discussed departing from the assumption
>> that a contributor should be able to build locally and primarily
>> check that the
Hello.
The situation with tool generated messages sent to
iss...@commons.apache.org
has gotten from bad to worse.
It's great that more and more work is reviewed by automated
tools and reports sent for every and all kinds of potentially
interesting nit of information.
It's not great, IMHO,
2020-07-22 21:21 UTC+02:00, Gary Gregory :
> On Wed, Jul 22, 2020 at 12:39 PM Rob Tompkins wrote:
>
>>
>>
>> > On Jul 22, 2020, at 11:53 AM, Gilles Sadowski
>> wrote:
>> >
>> > Le mer. 22 juil. 2020 à 17:45, Gary Gregory > <mailto:gary
2020-07-22 22:58 UTC+02:00, Olivier Lamy :
> On Thu, 23 Jul 2020 at 06:45, Gary Gregory wrote:
>
>> On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy wrote:
>>
>> > How do you deploy snapshots automatically?
>> >
>>
>> I don't use snapshots. If I have to have one, I build it locally.
>>
>
> But what
Hi.
2020-07-22 21:48 UTC+02:00, Gary Gregory :
> Hi All:
>
> There are three build systems available to us:
>
> - Apache Jenkins
> - GitHub Actions
> - Travis CI
> - Plus, *your *PC (that one does not really count.)
I don't agree: a source distribution assumes that one's own
computing resources
Hi.
2020-07-22 18:32 UTC+02:00, Stefan Bodewig :
> I hope anybody sees this message.
I've seen it. Although it could have been easily drowned in the flood. ;-)
> Can we please discuss this per component? I personally do like the idea
> of dependabot for applications but feel it is completly
Le mer. 22 juil. 2020 à 18:39, Rob Tompkins a écrit :
>
>
>
> > On Jul 22, 2020, at 11:53 AM, Gilles Sadowski wrote:
> >
> > Le mer. 22 juil. 2020 à 17:45, Gary Gregory > <mailto:garydgreg...@gmail.com>> a écrit :
> >>
> >> You can ign
hub automation to help us stay up to
> > date with dependencies.
> >
> > -Rob
> >
> > > On Jul 22, 2020, at 10:43 AM, Gilles Sadowski
> > wrote:
> > >
> > > Hello.
> > >
> > > What's this flood of emails about?
> > >
Le mer. 22 juil. 2020 à 17:39, Matt Sicker a écrit :
>
> I think it depends on the specific dependency. Maven plugins can typically
> be upgraded. Test dependencies, too.
Then why isn't this "feature" only enabled for "commons-parent"?
If a component has overridden a version provided by CP,
Le mer. 22 juil. 2020 à 17:19, Gary Gregory a écrit :
>
> On Wed, Jul 22, 2020 at 11:02 AM Gilles Sadowski
> wrote:
>
> > Hello.
> >
> > What's this flood of emails about?
> >
>
> Just read them!
I did a couple, and this is not really helpful:
---CUT---
Hello.
Le mer. 22 juil. 2020 à 16:54, Xeno Amess a écrit :
>
> as title.
> I see some dependency trying to upgrade from v1 to v2.3.1, and some plugin
> from 3.5.1 to 5.1.1
> Just confused.
I don't even know what this is all about...
Gilles
Hello.
What's this flood of emails about?
Gilles
Le mer. 22 juil. 2020 à 16:35, Rob Tompkins a écrit :
>
> I’m happy to merge them….will get to them by tomorrow morning ok?
>
> -Rob
-
To unsubscribe, e-mail:
Hello.
Le jeu. 16 juil. 2020 à 06:08, Matt Juntunen
a écrit :
>
> We have been working hard to prepare Apache Commons Geometry for an initial
> release, so I would like to release Apache Commons Geometry (full
> distribution) 1.0-beta1.
>
> Apache Commons Geometry 1.0-beta1 RC3 is available
Hello.
Le ven. 17 juil. 2020 à 00:37, Rob Tompkins a écrit :
>
> Woof….lots of submodules make for hard signature validation of the maven
> signatures.
I still don't get why this check cannot be automated (cf. other thread on that
subject where the same question remained unanswered).
> Will
Hi.
Le jeu. 16 juil. 2020 à 06:08, Matt Juntunen
a écrit :
>
> We have been working hard to prepare Apache Commons Geometry for an initial
> release, so I would like to release Apache Commons Geometry (full
> distribution) 1.0-beta1.
>
> Apache Commons Geometry 1.0-beta1 RC3 is available for
Hi.
Le lun. 13 juil. 2020 à 11:12, Mark Thomas a écrit :
>
> On 13/07/2020 06:43, Stefan Bodewig wrote:
> > On 2020-07-12, Rob Tompkins wrote:
> >
> >> given the consistency of the signatures from the plugins…do we need to
> >> check them for releases anymore?
> >
> > Yes, please. Not everybody
Hi.
Le mar. 7 juil. 2020 à 03:59, Matt Juntunen
a écrit :
>
> This needs to be cancelled again, at the very least to revert a change that
> Gilles was not in favor of.
Sorry for that (kind of).
The point was that a release vote thread is not meant to push further
changes if they are not
uld perhaps avoid even declaring
a class. [It could reduce the number of errors in future
compatibility checks.]
Regards,
Gilles
>
> -Matt
>
>
>
>
>
>
> From: Gilles Sadowski
> Sent: Sunday, July 5, 2020 2:12 PM
> To: Commons Developers Li
Hello.
Le lun. 6 juil. 2020 à 18:52, Xeno Amess a écrit :
>
> Hi.
> I tried to write a guide line document for this thing we discussed.
> Fell free to use it in any repo you want.
> And also feel free to continue the discussion,
The log is written by humans for humans to read. Should it really
> When I use fix I mean the original javadoc is wrong in format or meaning,
> > > and this pr aims to fix it.
> > > When I use refine I mean the original javadoc is correct, or at least
> > > correct in format, but we make it better in this pr.
> > > When I us
t
> > sometimes on functions.
> > So I do not think the verb can be deleted.
> > However, if you passed a ruleset or law or something about this, and pin it
> > to CONTRIBUTION.md，then I will try to follow.
> >
> >
> >
> >
> > G
his, and pin it
> to CONTRIBUTION.md，then I will try to follow.
See above.
Thanks,
Gilles
>
> Gilles Sadowski 于 2020年7月6日周一 上午2:29写道：
>
> > Hi Matt.
> >
> > Le dim. 5 juil. 2020 à 13:39, Matt Juntunen
> > a écrit :
> > >
> > > Yes, I should ha
> -Matt
> ____
> From: Gilles Sadowski
> Sent: Sunday, July 5, 2020 4:00 AM
> To: Commons Developers List
> Subject: [All][Geometry] Commit log (Was: [GitHub] ...)
>
> Hello.
>
> I'd like to collect some opinions about enforcing a minimal for
Hi.
Le dim. 5 juil. 2020 à 13:26, Matt Juntunen
a écrit :
>
> What are your objections to the name? The new name is more consistent with
> JDK conventions.
It is a programming error (as opposed to a usage error, which
subclasses of "RuntimeException" represent). As such it is
more
-1
Personally, I don't agree with the rationale.
Anyways, such a change must be proposed on the "dev" ML and, if
agreed upon, be related to a JIRA report.
Regards,
Gilles
Le sam. 4 juil. 2020 à 13:44, a écrit :
>
> This is an automated email from the ASF dual-hosted git repository.
>
>
Hello.
I'd like to collect some opinions about enforcing a minimal form in
commit messages.
My preference is that a log message is either
* terse, when the commit is trivial (e.g. "Javadoc" or "Unused variable"), or
* detailed but factual, if the change is not obvious.
IMHO, a commit message
Hello.
Le mar. 30 juin 2020 à 18:29, Matt Juntunen a écrit :
>
> Hi Baljit,
>
> The only things keeping the release from happening at this time are
>
> 1. the legal issue of including a 3D model which I opened a ticket for in
> JIRA yesterday [1], and
It doesn't look like this site
Hi.
2020-06-22 8:21 UTC+02:00, Bhawna Sharma <94sharmabha...@gmail.com>:
> PR has already one approval. Let me know if we are good to merge it now.
> https://github.com/apache/commons-math/pull/146
Merged.
Some parts of the library are (relatively) very old; the presence
of usage patterns that
Hello.
Le dim. 21 juin 2020 à 13:11, Bhawna Sharma <94sharmabha...@gmail.com> a écrit :
>
> Hey,
> Fifteen days back, I have raised one PR for Apache common math library.
Thanks for your interest in the project.
> Please find the URL https://github.com/apache/commons-math/pull/146
> It will be
Hello.
Le mer. 17 juin 2020 à 04:22, Matt Juntunen
a écrit :
>
> Hi Sven,
>
> If the createVertices and createFacets methods don't construct convex
> polygons then perhaps you could bypass them completely and just construct the
> tree directly from the boundaries. Assuming that I understand
Hi.
2020-06-13 16:57 UTC+02:00, Amey Jadiye :
> Hello Gilles,
>
> On Sat, Jun 13, 2020 at 6:36 PM Gilles Sadowski
> wrote:
>
>> Hello.
>>
>> After the migration from SVN to "gitbox", we noticed that the
>> _first_ build failed due to 3 unit
omponent; at least, it was right for this component to be
in the sand-box. ;-)
Personally, I'd forget about the history prior to the move to
git (viewed as the "initial" state from a source code donation),
fix the issues and start refactoring.
Regards,
Gilles
>
> Gilles Sadowski 于2020年6月13日周六
Hello.
After the migration from SVN to "gitbox", we noticed that the
_first_ build failed due to 3 unit tests not passing (see e.g. the
Travis report referred to the JIRA report[1]).
The move to "git" was intended to make it easier for people
willing to revive the [Graph] project.
IMO, the top
2020-06-13 4:05 UTC+02:00, Xeno Amess :
>> This discussion requires another thread.
>
> Well I don't think so, as I think this thread aims for making travis-ci can
> pass.
No; this thread was about setting up Travis (as asked by Amey).
> [...]
7:27写道：
>
>> Two failures and one error actually.
>> I will try to fetch the latest commit who CAN pass junit test, using
>> binary search.
>> Will send mail when I finish.
>>
>> Gilles Sadowski 于2020年6月13日周六 上午6:21写道：
>>
>>> Hi.
>>>
>>&g
Hi.
2020-06-12 21:43 UTC+02:00, Amey Jadiye :
> On Fri, Jun 12, 2020 at 4:40 PM Gilles Sadowski
> wrote:
>
>> 2020-06-12 12:32 UTC+02:00, Xeno Amess :
>> > Hi.
>> > I see the current travis-ci scripts.
>> > Do we really care only jdk8?
>> > Shou
601 - 700 of 2452 matches
Mail list logo
