Re: [ALL] CI builds

Hi. 2020-07-23 5:17 UTC+02:00, Matt Sicker : > If we request the pipeline template plugin to be installed, that would help > reduce the amount of boilerplate needed in the new Jenkins. I could help > with that. I don't know what part of this discussion this is a follow-up to, but I for sure

[All] Which is Commons's "issue-tracking system"?

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

Re: [ALL] CI builds

If we request the pipeline template plugin to be installed, that would help reduce the amount of boilerplate needed in the new Jenkins. I could help with that. 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

Re: [ALL] CI builds

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

Re: [all] Dependabot PRs

Guys...let’s not argue like this. It gets us nowhere. -Rob > On Jul 22, 2020, at 10:16 PM, Gilles Sadowski wrote: > > 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

Re: [all] Dependabot PRs

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

Re: [ALL] CI builds

> > > I realize that a local build seems to be your gold standard. > > Not mine. "Commons". > You are arguing for it. I would just call it a current policy or practice. > > That's a very debatable point of view. > > There was no debate. Yet it is a debatable point of view :) > I don't see

Re: [VOTE] Release Apache Commons Text 1.9 based on RC1

+1 it all checks out. -Rob > On Jul 21, 2020, at 4:57 PM, Gary Gregory wrote: > > Hi All, > > We have fixed a few bugs and added some enhancements since Apache Commons > Text 1.8 was released, so I would like to release Apache Commons Text 1.9. > > Apache Commons Text 1.9 RC1 is available

Re: [ALL] CI builds

@gilles I don't have a apache gitbox account, and nearly cannot do anything on gitbox. So it seems a mirror question to yours. Gilles Sadowski 于 2020年7月23日周四 上午8:46写道： > 2020-07-23 1:22 UTC+02:00, Torsten Curdt : > >> > >> > It does not mean that a source distribution goes away. > >> > >> Nor

Re: [VOTE] Create additional mailing lists for automated posts

+1. since I have no right to merge them, and have no interest in seeing these prs. I think only people who have the right to merge must see these past. Rob Tompkins 于 2020年7月23日周四 上午8:06写道： > -0.5 (real close to -1). Automated emails to commits@ is just part of > being part of the project.

Re: [VOTE] Release Apache Commons Text 1.9 based on RC1

  [x] +1 Release these artifacts Build passed on JDK 8 Ubuntu LTS, site reports generated and look OK. Checked dist area signatures and found no issues. Cheers Bruno On Wednesday, 22 July 2020, 8:57:06 am NZST, Gary Gregory wrote: Hi All, We have fixed a few bugs and added some

Re: [all] Dependabot PRs

> > > > 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. And I see two possible actions here: 1. A person of another project doing a release, triggering a bot to notify us and even

Re: [VOTE] Create additional mailing lists for automated posts

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

Re: [ALL] CI builds

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

Re: [ALL] CI builds

github ci is good when it green. But when it red, and you need to see the log, it become disgusting. It have a disgusting UI design, with an ugliest and slowest scrollbar. Olivier Lamy 于 2020年7月23日周四 上午7:54写道： > On Thu, 23 Jul 2020 at 09:30, Gary Gregory wrote: > > > On Wed, Jul 22, 2020 at

Re: [all] Dependabot PRs

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 than >> >> above? >> >> >> > >> > You just sent me a

Re: [VOTE] Create additional mailing lists for automated posts

-0.5 (real close to -1). Automated emails to commits@ is just part of being part of the project. Right? -Rob > On Jul 22, 2020, at 7:34 PM, Gary Gregory wrote: > > -0: We already have issues@ for automated emails. Whether it's automated > from one place or another does not matter (to me). >

Re: [VOTE] Create additional mailing lists for automated posts

2020-07-23 1:27 UTC+02:00, Gary Gregory : > -0: We already have issues@ for automated emails. Whether it's automated > from one place or another does not matter (to me). > > "If I'm not mistaken, the issues@ ML was intended to keep one > posted of and reactive on a human discussion happening on >

Re: [ALL] CI builds

On Thu, 23 Jul 2020 at 09:30, Gary Gregory wrote: > On Wed, Jul 22, 2020 at 4:59 PM Olivier Lamy wrote: > > > 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? > > > > > >

Re: [all] Dependabot PRs

On Wed, Jul 22, 2020 at 6:51 PM 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 than > >> above? > >> > > > > You just sent me a message I didn't want - and I need to delete it now ;) >

Re: [ALL] CI builds

On Wed, Jul 22, 2020 at 5:35 PM Gilles Sadowski wrote: > 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.) > >

Re: [VOTE] Create additional mailing lists for automated posts

also a -0 from me ...and a +1 to all what Gary said

Re: [all] Dependabot PRs

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 than > >> above? > >> > > > > You just sent me a message I didn't want - and I need to delete it now ;) >

Re: [ALL] CI builds

On Wed, Jul 22, 2020 at 4:59 PM Olivier Lamy wrote: > 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.

Re: [VOTE] Create additional mailing lists for automated posts

-0: We already have issues@ for automated emails. Whether it's automated from one place or another does not matter (to me). "If I'm not mistaken, the issues@ ML was intended to keep one posted of and reactive on a human discussion happening on JIRA." That's what dev@ is for IMO, humans. I've

Re: [ALL] CI builds

> > > 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 didn't sit well with you. Misunderstood. > > We

Re: [all] Dependabot PRs

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

Re: [ALL] CI builds

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

[VOTE] Create additional mailing lists for automated posts

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,

Re: [all] Dependabot PRs

> > 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 generate traffic that are caused by other people. If you

Re: [ALL] CI builds

> > 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 reports generated comply with the level of > quality

Re: [all] Dependabot PRs

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 > > a écrit : >> >> >> >> You can ignore

Re: [ALL] CI builds

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

Re: [ALL] CI builds

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

Re: [commons-compress] branch master updated: Enable GitHub Dependabot.

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

Re: [ALL] CI builds

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 about the community who wants to try snapshots build?

Re: [ALL] CI builds

Hi, I've been using GitHub actions for a while now, and it works fine. It's really handy to have CI and code in GitHub. I believe even users not using GitHub (i.e. no GitHub account) are able to access the CI logs, just like Travis. I never gave much thought to the Coveralls and JaCoCo issue.

Re: [ALL] CI builds

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. Gary > > On Thu, 23 Jul 2020 at 05:48, Gary Gregory wrote: > > > Hi All: > > > > There are three build systems available to

Re: [ALL] CI builds

How do you deploy snapshots automatically? On Thu, 23 Jul 2020 at 05:48, Gary Gregory wrote: > 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.) > > We have components building

[ALL] CI builds

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.) We have components building here and there, with multiple components building on multiple systems. My main driver is that we already use

Re: [all] Dependabot PRs

> On Jul 22, 2020, at 3:26 PM, Gary Gregory wrote: > > On Wed, Jul 22, 2020 at 1:58 PM Torsten Curdt wrote: > >>> >>> >> You can ignore those > > How can I ignore stuff that gets pushed into my mailbox? > Spammers could argue in the same way. > I've had to click on

Re: [all] Dependabot PRs

On Wed, Jul 22, 2020 at 1:58 PM Torsten Curdt wrote: > > > > > > > >> You can ignore those > > > > > > > > How can I ignore stuff that gets pushed into my mailbox? > > > > Spammers could argue in the same way. > > > > I've had to click on each of these automated messages to > > > > delete them.

Re: [all] Dependabot PRs

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 > a écrit : > >> > >> You can ignore those > > > > How can I ignore stuff that gets pushed into

Re: [all] Dependabot PRs

> > > > >> You can ignore those > > > > > > How can I ignore stuff that gets pushed into my mailbox? > > > Spammers could argue in the same way. > > > I've had to click on each of these automated messages to > > > delete them. IMHO, the consequences of new settings > > > should be tested on a

Re: [all] Dependabot PRs

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 > > a écrit : > >> > >> You can ignore those > > > > How can I ignore stuff that gets pushed

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

I don’t see why not here, given that it would go in to the master branch (which is our main development line). Clearly we wouldn’t want to auto release in such a state. -Rob > On Jul 22, 2020, at 11:49 AM, Melloware wrote: > > Gary, > > I am a huge +1 on this feature for all those reasons.

Re: [commons-compress] branch master updated: Enable GitHub Dependabot.

I hope anybody sees this message. Can we please discuss this per component? I personally do like the idea of dependabot for applications but feel it is completly wrong for libraries and would prefer to not use it. Stefan - To

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

To answer the question of your subject: my opinion is a very strong NO. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [all] Dependabot PRs

On 2020-07-22, Rob Tompkins wrote: > I’m happy to merge them….will get to them by tomorrow morning ok? TBH I'd prefer to turn them off and reject the PRs. Personally I don't see any value for our downstream users if we update our dependencies without actually needing an update - with the

Re: [all] Dependabot PRs

> On Jul 22, 2020, at 11:53 AM, Gilles Sadowski wrote: > > Le mer. 22 juil. 2020 à 17:45, Gary Gregory > a écrit : >> >> You can ignore those > > How can I ignore stuff that gets pushed into my mailbox? > Spammers could argue in the same way. > I've had to

Re: [all] Dependabot PRs

Le mer. 22 juil. 2020 à 17:45, Gary Gregory a écrit : > > You can ignore those How can I ignore stuff that gets pushed into my mailbox? Spammers could argue in the same way. I've had to click on each of these automated messages to delete them. IMHO, the consequences of new settings should be

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

Gary, I am a huge +1 on this feature for all those reasons.  Nice work! Mello On 7/22/2020 11:34 AM, Gary Gregory wrote: Hi, There is no telling what any version change means to any library generically. We can only assume that some people follow semver and don't break BC. But there is no

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

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,

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

They started a bot to auto generate pr about dependency upgrade... Gilles Sadowski 于2020年7月22日周三 下午11:33写道： > 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

Re: [all] Dependabot PRs

You can ignore those if you prefer to look at the GitHub PRs instead. That's what I do. Gary On Wed, Jul 22, 2020 at 11:20 AM Rob Tompkins wrote: > I think that Gary tuerned on some github automation to help us stay up to > date with dependencies. > > -Rob > > > On Jul 22, 2020, at 10:43 AM,

Re: [all] Dependabot PRs

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--- dependabot[bot] opened a new pull request

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

Hi, There is no telling what any version change means to any library generically. We can only assume that some people follow semver and don't break BC. But there is no guarantee. IMO, it's better for Dependabot to make us aware of any change available. We also have the benefits of the PRs being

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

I think it depends on the specific dependency. Maven plugins can typically be upgraded. Test dependencies, too. On Wed, Jul 22, 2020 at 10:12 Xeno Amess wrote: > 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. > --

Re: [all]should we really allow denpabot upgrade a dependency that changes major version?

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

Re: [all] Dependabot PRs

On Wed, Jul 22, 2020 at 11:02 AM Gilles Sadowski wrote: > Hello. > > What's this flood of emails about? > Just read them! Gary > > 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 > >

Re: [all] Dependabot PRs

I think that Gary tuerned on some github 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? > > Gilles > > Le mer. 22 juil. 2020 à 16:35, Rob Tompkins a écrit : >> >> I’m

[all]should we really allow denpabot upgrade a dependency that changes major version?

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.

Re: [all] Dependabot PRs

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:

[all] Dependabot PRs

I’m happy to merge them….will get to them by tomorrow morning ok? -Rob - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org