Hello,
I start the process to do the RC1 of 3.0.
Ping me on freenode.org, channel #jmeter if needs
Milamber
On 12/04/2016 19:20, Milamber wrote:
Hello,
I will start the RC process for 3.0RC1 next Saturday (16th)
With all changes in this version, we need to update a lot of
screenshots before the RC (see Bug 59126). I will try to do this
before Saturday.
Milamber
On 12/04/2016 13:50, Philippe Mouawad wrote:
Hi,
I cannot merge before thursday evening.
Anybody else can ?
Milamber when do you plan to make the release ?
Should we merge those or wait for 3.1 ?
Regards
On Monday, April 11, 2016, Antonio Gomes Rodrigues <[email protected]>
wrote:
Hi all,
I have made some PR to allow the user have a better experience with 3.0
If it's possible, one of you can check my PR and merge it if it's ok
before
3.0 release?
Thanks
Antonio
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2200-b
Garanti
sans virus. www.avast.com
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2200-b
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
2016-04-04 23:14 GMT+02:00 Milamber <[email protected]
<javascript:;>>:
On 04/04/2016 14:23, Philippe Mouawad wrote:
Hi,
As it appears there is no pending issue to release a 3.0, any
volunteer
to
act as RM for 3.0 ?
Yes, with great pleasure for this great new version!
I can start a release process next Saturday (or Sunday)
Milamber
Regards
Philippe
On Sunday, April 3, 2016, Philippe Mouawad
<[email protected]
<javascript:;>>
wrote:
As suggested by Felix, I think this enhancement can be delayed to
next
release following 3.0.
If so, @sebb and all, can we start the release process ?
Regards
On Saturday, April 2, 2016, Philippe Mouawad <
[email protected] <javascript:;>
<javascript:_e(%7B%7D,'cvml','[email protected]
<javascript:;>');>> wrote:
On Saturday, April 2, 2016, sebb <[email protected] <javascript:;>>
wrote:
On 1 April 2016 at 23:58, Philippe Mouawad <
[email protected] <javascript:;>>
wrote:
It's developed.
I know.
Just need to decide which option is best.
Not possible to decide without knowing how expensive the
options are.
the first option (LRU like) is expensive as per Vladimir notes.
We could reduce cost by dropping every N additions.
But bear in mind that cost start to be high when we reach the
limit,
without it GC would have a cost as memory would keep increasing.
But it is hard to make a comparison
Option 2 (warn and stop adding) has nearly 0 overhead
As I wrote, that needs to be resolved.
But we can delay its integration if needed
Regardd
On Friday, April 1, 2016, sebb <[email protected] <javascript:;>>
wrote:
On 1 April 2016 at 22:37, Philippe Mouawad <
[email protected] <javascript:;>
<javascript:;>> wrote:
hello,
I think trunk is now ready for a release.
I see no pending bug and I think 3.0 is really expected.
What about the OOM issue?
That either needs to be resolved or postponed.
Are you ok to start ?
Thanks
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
