IMO "domant" is just an indication of a status. If someone goes and
keeps on working stuff ... well ... then that status is nullified by
merit. (not through a single commit though) I don't see a reason to
forbid svn access ...that's the wrong signal. We just need to agree
and maintain and communica
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
+1.
I still expect us to send truly dead items to the Attic.
Hen
On Mon, May 16, 2011 at 10:52 AM, Phil Steitz wrote:
> I would like to take the proposal made in [1], modified per
> discussion on that thread to a VOTE, so we can start implementing
> the policy.
>
> The provisions are as follows
On 5/16/11 4:21 PM, sebb wrote:
> On 17 May 2011 00:07, Gary Gregory wrote:
>> On Mon, May 16, 2011 at 5:57 PM, Paul Libbrecht wrote:
>>
>>> So we should relaunch a vote?
>>> (or... I should vote a no and relaunch?)
>>>
>>> paul
>>>
>>>
>>> Le 16 mai 2011 à 23:44, Phil Steitz a écrit :
>>>
>>
On 5/16/11 3:47 PM, Gilles Sadowski wrote:
> On Mon, May 16, 2011 at 02:39:01PM -0700, Phil Steitz wrote:
>> On 5/16/11 3:44 AM, Dr. Dietmar Wolz wrote:
>>> Nikolaus Hansen, Luc and me discussed this issue in Toulouse.
> Reading that, I've been assuming that...
>
>>> We have two options to handle t
+ 1 with change to d to be "svn is open but no release without a vote".
Ralph
On May 16, 2011, at 10:52 AM, Phil Steitz wrote:
> I would like to take the proposal made in [1], modified per
> discussion on that thread to a VOTE, so we can start implementing
> the policy.
>
> The provisions are a
On 17 May 2011 00:07, Gary Gregory wrote:
> On Mon, May 16, 2011 at 5:57 PM, Paul Libbrecht wrote:
>
>> So we should relaunch a vote?
>> (or... I should vote a no and relaunch?)
>>
>> paul
>>
>>
>> Le 16 mai 2011 à 23:44, Phil Steitz a écrit :
>>
>> >>> d) svn remains open (but no commits witho
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8386&projectId=107
Build statistics:
State: Error
Previous State: Ok
Started at: Mon 16 May 2011 23:20:31 +
Finished at: Mon 16 May 2011 23:20:32 +
Total time: 0s
Build Trigger: Schedule
Build Num
On Mon, May 16, 2011 at 5:57 PM, Paul Libbrecht wrote:
> So we should relaunch a vote?
> (or... I should vote a no and relaunch?)
>
> paul
>
>
> Le 16 mai 2011 à 23:44, Phil Steitz a écrit :
>
> >>> d) svn remains open (but no commits without revival vote)
> >> It seems slightly too harsh to me
On Mon, May 16, 2011 at 02:39:01PM -0700, Phil Steitz wrote:
> On 5/16/11 3:44 AM, Dr. Dietmar Wolz wrote:
> > Nikolaus Hansen, Luc and me discussed this issue in Toulouse.
Reading that, I've been assuming that...
> > We have two options to handle this kind of failure in tests of stochastic
> > o
On 5/16/11 2:57 PM, Paul Libbrecht wrote:
> So we should relaunch a vote?
> (or... I should vote a no and relaunch?)
Lets see how others respond. There may be other changes...
Phil
> paul
>
>
> Le 16 mai 2011 à 23:44, Phil Steitz a écrit :
>
d) svn remains open (but no commits without rev
On 5/13/11 11:25 PM, Phil Steitz wrote:
> On 5/13/11 12:05 PM, ma...@apache.org wrote:
>> Author: markt
>> Date: Fri May 13 19:05:20 2011
>> New Revision: 1102868
>>
>> URL: http://svn.apache.org/viewvc?rev=1102868&view=rev
>> Log:
>> Add the ability to register an interest in a key to prevent the
So we should relaunch a vote?
(or... I should vote a no and relaunch?)
paul
Le 16 mai 2011 à 23:44, Phil Steitz a écrit :
>>> d) svn remains open (but no commits without revival vote)
>> It seems slightly too harsh to me.
>> Since jelly is among the heaviest targeted ones here, I think the wh
On 5/16/11 2:34 PM, Paul Libbrecht wrote:
> Sorry Phil,
>
> I missed that one. I would like to adjust that policy at line:
>>d) svn remains open (but no commits without revival vote)
> It seems slightly too harsh to me.
> Since jelly is among the heaviest targeted ones here, I think the whole
On 5/16/11 3:44 AM, Dr. Dietmar Wolz wrote:
> Nikolaus Hansen, Luc and me discussed this issue in Toulouse.
> We have two options to handle this kind of failure in tests of stochastic
> optimization algorithms:
> 1) fixed random seed - but this reduces the value of the test
> 2) Using the RetryRu
Sorry Phil,
I missed that one. I would like to adjust that policy at line:
>d) svn remains open (but no commits without revival vote)
It seems slightly too harsh to me.
Since jelly is among the heaviest targeted ones here, I think the whole
dormancy aspect would fit but preventing commits so
+1
-Rahul
On Mon, May 16, 2011 at 1:52 PM, Phil Steitz wrote:
> I would like to take the proposal made in [1], modified per
> discussion on that thread to a VOTE, so we can start implementing
> the policy.
>
> The provisions are as follows:
>
> 0) To move a component to dormant requires a VOTE.
Hi all guys,
just to let you know that Luke Blanshard submitted the Software Grant
for OGNL, that should fix the legal issue regarding Luke's
contributions under BSD language.
Thanks to Henri and Phil for the guidance!
Moreover I invited him to submit the ICLA in order to be voted as OGNL
Committe
+1 for me, sounds a wise procedure
thanks!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, May 16, 2011 at 7:52 PM, Phil Steitz wrote:
> I would like to take the proposal made in [1], modified per
> discussion on that thread to a VOTE, so we can start implementing
Le 16/05/2011 16:19, Matt Benson a écrit :
On Sun, May 15, 2011 at 6:01 PM, Phil Steitz wrote:
On 5/15/11 9:43 AM, Luc Maisonobe wrote:
Le 15/05/2011 10:30, Mikkel Meyer Andersen a écrit :
+1
From me, too.
OK, it's done now. I have put everything as subpackages of
geometry as suggested by
I would like to take the proposal made in [1], modified per
discussion on that thread to a VOTE, so we can start implementing
the policy.
The provisions are as follows:
0) To move a component to dormant requires a VOTE. A single -1
suffices to postpone the action; but a -1 in a dormancy vote is
Hello,
Perso not blocker for me, the most important is to have easy setup for
ide and checkstyle files configured and not loose to much time with
that.
IMHO it's just a "taste" question (in my country some prefers Bordeaux
and others Bourgogne :-) ).
/Olivier
2011/5/16 Simone Tripodi :
> Hi Maur
The invalid link has been fixed:
URL: http://svn.apache.org/viewvc?rev=1103703&view=rev
Log:
Fix relative link for mail-lists
Also fixed in the html.
-- Forwarded message --
From: Mohamed M. El-Beltagy
Date: 15 May 2011 23:29
Subject: Commons Dormant mailing lists
To: "infrastru
Hi Matthiew,
If I've not already mentioned this, make sure you get good coverage for the
code to be included. You can see the code coverage report in the generated
site, for example http://commons.apache.org/codec/cobertura/index.html
Gary
On Mon, May 16, 2011 at 8:00 AM, Matthew Pocock <
turing
On Sun, May 15, 2011 at 6:01 PM, Phil Steitz wrote:
> On 5/15/11 9:43 AM, Luc Maisonobe wrote:
>> Le 15/05/2011 10:30, Mikkel Meyer Andersen a écrit :
>>> +1
From me, too.
>>
>> OK, it's done now. I have put everything as subpackages of
>> geometry as suggested by Phil, and I have taken care
Hi Gary,
I will see how much extra work is involved in also implementing D-M. I'm
only contracted to port B-M, but if it's not oodles of extra work I'll do
D-M also.
Matthew
On 16 May 2011 12:50, Gary Gregory wrote:
> Hi Mathew,
>
> Will you also provide a Daitch–Mokotoff Soundex for compariso
> In fact, I've only ever seen "testMaximize" and (less often) "testRosen"
> fail. So, for the time being, I'd add "@Retry" to those only.
+1 for adding @Retry to the two tests occasionally failing
-
To unsubscribe, e-mail: de
Hi Mathew,
Will you also provide a Daitch–Mokotoff Soundex for comparison?
Gary
On May 16, 2011, at 7:17, Matthew Pocock
wrote:
Beider-Morse
On Mon, May 16, 2011 at 12:44:45PM +0200, Dr. Dietmar Wolz wrote:
> Nikolaus Hansen, Luc and me discussed this issue in Toulouse.
> We have two options to handle this kind of failure in tests of stochastic
> optimization algorithms:
> 1) fixed random seed - but this reduces the value of the test
Hi,
Sorry to be slow getting back to you. Thanks for all the helpful feedback.
The codec implements Beider-Morse Phonetic Matching which is optimised for
sounds-like in family names, particularly Central/Eastern European and
Jewish names. I'm in the process of contacting all the relevant people ab
I'm +1 on using @Retry instead of fixed seed.
2011/5/16 Dr. Dietmar Wolz :
> Nikolaus Hansen, Luc and me discussed this issue in Toulouse.
> We have two options to handle this kind of failure in tests of stochastic
> optimization algorithms:
> 1) fixed random seed - but this reduces the value of
Nikolaus Hansen, Luc and me discussed this issue in Toulouse.
We have two options to handle this kind of failure in tests of stochastic
optimization algorithms:
1) fixed random seed - but this reduces the value of the test
2) Using the RetryRunner - preferred solution
@Retry(3) should be suffici
Hi Maurizio!
indeed, sometimes such style makes me smile because brings back old memories :)
Well, I was too young at '90 to program - anyway I was a SuperMario
champion - but my professors at University used that style :P
Jokes a part, I thought that code style was a trivial topic, but at
this po
Phil probably hit the nail on the head: contributors might have
problem to incorporate patches, the main risk is that every patch
contain a lot of noise and it's not good for the sake of reviewing.
I have no problem with most of the conventions (which are the default
settings of IntelliJ IIRC).
The
Hi guys,
thanks for the feedbacks!!! I understand your concerns, the main
reason behind such proposal is that OGNL already adopted a style that
matches, in the bigger part of the cases, to Maven style, so I thought
it would have been nice having a unique code style.
Simo
http://people.apache.org/~
Thanks for your help Konstantin!!!
the "simple" problem is that the bigger part of tests inherit from
OgnlTestCase that are ctors-based parametrized test cases (they launch
the Suite), so when porting it to JUnit4 using the
@RunWith(Parameterized.class), half tests are broken :/
Simo
http://people
37 matches
Mail list logo
