Re: [lang] Todo utility class

Hi. On Wed, 14 Mar 2018 16:51:43 -0500, Matt Benson wrote: I have often thought about creating a utility class that allows me to write skeletal code that still compiles but will remind me to go back and finish it. This is a weird meta area of programming, but here are some basic usage

Re: Github usage

Thanks for all the suggestions. I see that there are things to try before bothering INFRA. ;-) Regards, Gilles On Thu, 15 Mar 2018 14:03:35 -0400, Otto Fowler wrote: https://github.com/apache/metron/tree/master/dev-utilities/committer-utils if you just want the bash On March 15, 2018 at

[ANNOUNCE] Commons Parent 45 released.

[This announcement is only going to the dev list.] Hello All, Commons Parent 45 has been released. The change from release 44 is: - Rearranging plugin order in -Prelease, removing commons-release-plugin from build>pluginManagement The changes from release 43 are: - new profile

Re: Github usage

https://github.com/apache/metron/tree/master/dev-utilities/committer-utils if you just want the bash On March 15, 2018 at 13:51:00, ajs6f (aj...@apache.org) wrote: One gotcha that has bit me before-- if the PR isn't rebased over the current master (assuming you are merging into master) it may

Re: Github usage

One gotcha that has bit me before-- if the PR isn't rebased over the current master (assuming you are merging into master) it may still be merge-able because maybe there aren't any conflicts. (E.g. maybe no one has worked on that section of the codebase since the PR's branch was branched.) But

Re: Github usage

Oh, I was looking at the wrong version of Debian I think. On 15 March 2018 at 11:01, Gilles wrote: > On Thu, 15 Mar 2018 10:39:50 -0500, Matt Sicker wrote: > >> I can't find that package on debian's package search page. >> > >

Re: Github usage

On Thu, 15 Mar 2018 10:39:50 -0500, Matt Sicker wrote: I can't find that package on debian's package search page. https://packages.debian.org/stretch/git-hub I'm not sure if they package it there There is a slew of golang-related packages. (it's a go program, so it's pretty easy to

Re: Github usage

I can't find that package on debian's package search page. I'm not sure if they package it there (it's a go program, so it's pretty easy to install if you have go already). Here's the official site: https://hub.github.com/ On 15 March 2018 at 10:19, Gilles wrote: >

Re: Github usage

Hi. On Wed, 14 Mar 2018 11:27:38 -0500, Matt Sicker wrote: When you have a GitHub origin, you can checkout pulls/42/head to check out PR#42. You can pull/merge from that branch as well to merge the PR (by committing and pushing that merge, GitHub will notice and mark the PR as merged). You

Re: [DISCUSS] new component for timing?

2018-03-15 14:36 GMT+01:00 Otto Fowler : > If we can come to consensus on the way forward, I’ll be happy to do the > work ( although I’ll need help of course ). > I guess I’m the straw that broke the camel’s back then? ;) > > > > > On March 15, 2018 at 08:09:45, Gilles

[RESULT][LAZY][VOTE] Release Commons Parent 45 based on RC1.

This [LAZY][VOTE] passes with the following votes: Gary Gregory: +1, Rob Tompkins: +1 I will promote the requisite artifacts. -Rob > On Mar 12, 2018, at 8:49 AM, Rob Tompkins wrote: > > Hello all, > > This is a [LAZY][VOTE] for releasing Apache Commons Parent 45 (from

Re: [LAZY][VOTE] Release Commons Parent 45 based on RC1.

Here’s my +1 based upon my doing a dry run for the text release locally. -Rob > On Mar 12, 2018, at 8:49 AM, Rob Tompkins wrote: > > Hello all, > > This is a [LAZY][VOTE] for releasing Apache Commons Parent 45 (from RC1). > [Pardon my miss in commons-parent-44-RC3, I am

Re: [DISCUSS] new component for timing?

If we can come to consensus on the way forward, I’ll be happy to do the work ( although I’ll need help of course ). I guess I’m the straw that broke the camel’s back then? ;) On March 15, 2018 at 08:09:45, Gilles (gil...@harfang.homelinux.org) wrote: Hi. On Thu, 15 Mar 2018 03:52:58 -0700,

Re: [DISCUSS] new component for timing?

Hi. On Thu, 15 Mar 2018 03:52:58 -0700, Otto Fowler wrote: I think bringing back commons-monitoring/sirota would only be possible if it were to be modular enough that you could bring in the ‘core’ classes without needing to bring in all of what sirota ended up being, which was an end to end

Re: [DISCUSS] new component for timing?

I think bringing back commons-monitoring/sirota would only be possible if it were to be modular enough that you could bring in the ‘core’ classes without needing to bring in all of what sirota ended up being, which was an end to end solution. commons-monitoring or commons-timing seem to be the