I've never like using versions like this :-(
Gary
On Wed, Apr 15, 2015 at 1:19 PM, Paul Benedict wrote:
> Odd way to use versions, imo. Sounds like "discussion" and "review patch"
> and "patch needed" tags would be the better tool.
>
>
> Cheers,
> Paul
>
> On Wed, Apr 15, 2015 at 3:18 PM, Dunca
On 15 April 2015 at 21:19, Paul Benedict wrote:
> Odd way to use versions, imo. Sounds like "discussion" and "review patch"
> and "patch needed" tags would be the better tool.
I completely agree. But this has how it's been done historically in
Lang, so I wasn't trying to rock the boat too much wi
Odd way to use versions, imo. Sounds like "discussion" and "review patch"
and "patch needed" tags would be the better tool.
Cheers,
Paul
On Wed, Apr 15, 2015 at 3:18 PM, Duncan Jones wrote:
> Hi folks,
>
> Currently the "Review Patch" fix version seems to be applied whenever
> code has been su
Hi folks,
Currently the "Review Patch" fix version seems to be applied whenever
code has been supplied in an issue. This includes situations where
agreement hasn't yet been reached on fixing the issue and where the
supplied "patch" is minimal at best.
I would prefer if we only use this marker on
On 04/14/2015 03:02 PM, Luc Maisonobe wrote:
> This is a [VOTE] for releasing Apache Commons Math 3.5 from release
> candidate 2.
>
> Changes since RC1 are:
> - fixed tests incompatibilities with Java 5
> - fixed warning messages from jgit buildnumber when building from
> .tar.gz or .zip a
James Carman and I had a brief conversation following my Apachecon
talk, where I mentioned the challenge we have around deciding what
to do about supporting multiple threads / processes. He has some
good ideas. This is really just a poke to get him to post those
ideas :)
The final presented slid
> On Apr 15, 2015, at 9:06 AM, Benedikt Ritter wrote:
>
> Hello Phil,
>
> 2015-04-15 14:44 GMT+02:00 Phil Steitz :
>
>> Whatever discussions have impact on the code should come to this list.
>> Please make sure that any discussion of patches at least gets echoed to
>> this list.
>
>
> Yes
Hello Phil,
2015-04-15 14:44 GMT+02:00 Phil Steitz :
> Whatever discussions have impact on the code should come to this list.
> Please make sure that any discussion of patches at least gets echoed to
> this list.
Yes, I need to take care of this. I need some spare time to put together a
request
Whatever discussions have impact on the code should come to this list. Please
make sure that any discussion of patches at least gets echoed to this list.
Regarding your question, I have never seen much value in the kind of nag you
are referring to. Just my 2c.
> On Apr 15, 2015, at 5:47 AM
Hi Bruno
2015-04-15 12:14 GMT+02:00 Bruno P. Kinoshita :
> Hi Benedikt,
>
> After playing more with [text] and some edit distances, I think we can
> retake this conversation and hopefully fix SANDBOX-488 [1].
>
> I've created a branch SANDBOX-488 in git [2] with the following
> modifications:
>
>
Hi all,
when using coveralls [1] one need to configure a test coverage threshold.
If a PR lowers the test coverage below this threshold, coveralls will send
a notification. This happened for PR 63 [2].
I'm about to create an issue for infra for configuring the threshold. But
I'm not sure what woul
On Wed, Apr 15, 2015 at 7:15 AM, Sergio Fernández wrote:
> On Wed, Apr 15, 2015 at 2:20 AM, Peter Ansell
> wrote:
> >
> > BlankNodes cannot be compared across different SPARQL queries. That is
> > a well known RDF issue, not just with SPARQL, and is not going to be
> > solved by anything except
GitHub user jamessawle opened a pull request:
https://github.com/apache/commons-lang/pull/63
Lang 740 - Memoizer implementation
Enclosed is an implementation of the Memoizer class, along with some unit
tests through the main flow of the code.
You can merge this pull request into a
Hi Benedikt,
After playing more with [text] and some edit distances, I think we can retake
this conversation and hopefully fix SANDBOX-488 [1].
I've created a branch SANDBOX-488 in git [2] with the following modifications:
* The StringMetric interface has been renamed to EditDistance* We have the
On Wed, Apr 15, 2015 at 2:20 AM, Peter Ansell
wrote:
>
> BlankNodes cannot be compared across different SPARQL queries. That is
> a well known RDF issue, not just with SPARQL, and is not going to be
> solved by anything except bulk execution of a single query to get all
> of the BlankNodes back in
15 matches
Mail list logo