You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gilles <gi...@harfang.homelinux.org> on 2016/09/22 11:13:49 UTC
[RNG] New implementations before release of 1.0
Hi.
Release of version 1.0 will be delayed for another two weeks,
waiting for additional implementations.
See:
https://issues.apache.org/jira/browse/RNG-16
https://issues.apache.org/jira/browse/RNG-17
If you intend to try and implement them, please assign the
issue to yourself.
Patches for other algorithms are welcome too.
Please note that any new implementation must come with
(1) a unit test where the output (say, a few hundred
numbers) of "Commons RNG" is compared against a
"reference" implementation,
(2) the outputs of the "RandomStressTester" piping
from the "Dieharder" and "TU01/BigCrush" actual
stress test suites.
If you provide the Java code and (1), I can take take care
of (2), since I have the software installed already.[1]
Regards,
Gilles
[1] Please take into account that it will take about 32
hours to run "BigCrush".
Hence, I'll start all the runs (3 "Dieharder" and 3
"BigCrush", per new implementation) in _one_ go.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [RNG] New implementations before release of 1.0
Posted by Gilles <gi...@harfang.homelinux.org>.
On Thu, 22 Sep 2016 17:50:23 +0200, J�rg Schaible wrote:
> Hi Gilles,
>
> Gilles wrote:
>
>> On Thu, 22 Sep 2016 14:29:37 +0200, J�rg Schaible wrote:
>>> Gilles wrote:
>>>
>>>> Hi.
>>>>
>>>> Release of version 1.0 will be delayed for another two weeks,
>>>> waiting for additional implementations.
>>>
>>> Then, please, cancel the still running vote also ;-)
>>
>> I'll do (the deadline was over anyways).
>
> The deadline just means that you wait to close the vote "at least"
> until.
I noticed that there are different formulation, with different
meanings.
But for that vote, the text said:
---CUT---
This vote will close in 72 hours, [...]
---CUT---
Regards,
Gilles
>
> Cheers,
> J�rg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [RNG] New implementations before release of 1.0
Posted by "Dennis E. Hamilton" <de...@acm.org>.
> -----Original Message-----
> From: Jörg Schaible [mailto:joerg.schaible@bpm-inspire.com]
> Sent: Thursday, September 22, 2016 08:50
> To: dev@commons.apache.org
> Subject: Re: [RNG] New implementations before release of 1.0
>
> Hi Gilles,
>
> Gilles wrote:
>
> > On Thu, 22 Sep 2016 14:29:37 +0200, Jörg Schaible wrote:
> >> Gilles wrote:
> >>
> >>> Hi.
> >>>
> >>> Release of version 1.0 will be delayed for another two weeks,
> >>> waiting for additional implementations.
> >>
> >> Then, please, cancel the still running vote also ;-)
> >
> > I'll do (the deadline was over anyways).
>
> The deadline just means that you wait to close the vote "at least"
> until.
[orcmid]
I think it is the vote will be *open* "at least until." It is common to leave a [VOTE] open either because of discussion or to see if an additional ballot is forthcoming. I've started using "ending no earlier than <some-UTC-datetime>" in [VOTE]s I run.
I suppose the way [VOTE] threads end clearly is either with a [CANCEL] report or a [RESULT] report.
>
> Cheers,
> Jörg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [RNG] New implementations before release of 1.0
Posted by Jörg Schaible <jo...@bpm-inspire.com>.
Hi Gilles,
Gilles wrote:
> On Thu, 22 Sep 2016 14:29:37 +0200, J�rg Schaible wrote:
>> Gilles wrote:
>>
>>> Hi.
>>>
>>> Release of version 1.0 will be delayed for another two weeks,
>>> waiting for additional implementations.
>>
>> Then, please, cancel the still running vote also ;-)
>
> I'll do (the deadline was over anyways).
The deadline just means that you wait to close the vote "at least" until.
Cheers,
J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [RNG] New implementations before release of 1.0
Posted by Gilles <gi...@harfang.homelinux.org>.
On Thu, 22 Sep 2016 14:29:37 +0200, J�rg Schaible wrote:
> Gilles wrote:
>
>> Hi.
>>
>> Release of version 1.0 will be delayed for another two weeks,
>> waiting for additional implementations.
>
> Then, please, cancel the still running vote also ;-)
I'll do (the deadline was over anyways).
Gilles
>
> Cheers,
> J�rg
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [RNG] New implementations before release of 1.0
Posted by Jörg Schaible <jo...@bpm-inspire.com>.
Gilles wrote:
> Hi.
>
> Release of version 1.0 will be delayed for another two weeks,
> waiting for additional implementations.
Then, please, cancel the still running vote also ;-)
Cheers,
J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org