Re: JMeter versions and release dates
A 5.4.2 would be great. A 5.5 could be harder, as there are usually some smaller things, that pop up. Felix Am 15. Dezember 2021 09:06:39 MEZ schrieb Milamber : >Hi, > >5.5 is ready to release or need some commits? > >I will prepare 5.4.2 (just fix Log4J) > >Milamber > >On 15/12/2021 09:04, Philippe Mouawad wrote: >> Hello Milamber, >> If you're available, it would be good to release: >> >> - 5.4.2 with just the fix for Log4J >> - 5.5 (fix+improvements) >> >> If not, just 5.5 >> >> Thanks >> >> On Wed, Dec 15, 2021 at 9:02 AM Milamber wrote: >> >>> Hi, >>> >>> Probably need to release ASAP a fix version? 5.4.1? (from tag with just >>> the fix for Log4J) or new version 5.5 (fix+improvements)? >>> >>> Milamber >>> >>> On 14/12/2021 21:42, Philippe Mouawad wrote: Hello, For information: - https://blogs.apache.org/security/entry/cve-2021-44228 Regards On Tuesday, December 14, 2021, Philippe Mouawad < p.moua...@ubik-ingenierie.com> wrote: > Hello, > For me both 6.0 and 5.5 are ok. > Regards > > On Tue, Dec 7, 2021 at 9:02 PM Milamber wrote: > >> Hi, >> >> Currently, I prefer release 5.5 as version, add deprecated elements if >> needed. >> >> for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 >> (or why not 17) (so with OpenJDK official support instead Oracle Java). >> Using recent openjdk allow improvements from java release. >> >> and for 6.0, add support for HTTP/2.0 request seems be a requirement. >> >> Milamber >> >> On 07/12/2021 19:07, Felix Schumacher wrote: >>> Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: > I would be fine with both versions 5.5 and 6.0. Same for me. I am limited in time :-/, so I would not be able to rename 5.5 -> >>> 6.0, so I would suggest releasing as 5.5, and going for 6.0 a bit later. I thought I could work on DSL this December, however, it turns out >>> not >> to be the case. > and more important a major version could be a good point to drop old > stuff I am afraid it does not work that way. If we want to drop something, we need to announce the deprecation >>> plan >> in advance. AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not deprecated), so there's no option to drop it yet. >>> That is what I meant. If we want to use the next major version to drop >>> things. 5.5 would be a good opportunity to mark those features as >>> deprecated. >>> >>> > so a 6.0 is not necessarily needed In 99% of the cases, the versions are there to convey the changes to >> the end-users. I really like realver: https://twitter.com/lorenc_dan/status/1209289792569131008 6.0 would mean "hey, there's something big, go and try it" :) >>> That is true, too :) >>> >>> Felix >>> Vladimir > -- > Cordialement > Philippe M. > Ubik-Ingenierie > >>> >
Re: JMeter versions and release dates
Hello, The Version log4j 2.15 is incomplete https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046 Anas On Wed, Dec 15, 2021 at 9:15 AM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > I think 5.5 is ready. > > Vladimir > -- Cordialement, - Anas OUFDOU
Re: JMeter versions and release dates
I think 5.5 is ready. Vladimir
Re: JMeter versions and release dates
Hi, 5.5 is ready to release or need some commits? I will prepare 5.4.2 (just fix Log4J) Milamber On 15/12/2021 09:04, Philippe Mouawad wrote: Hello Milamber, If you're available, it would be good to release: - 5.4.2 with just the fix for Log4J - 5.5 (fix+improvements) If not, just 5.5 Thanks On Wed, Dec 15, 2021 at 9:02 AM Milamber wrote: Hi, Probably need to release ASAP a fix version? 5.4.1? (from tag with just the fix for Log4J) or new version 5.5 (fix+improvements)? Milamber On 14/12/2021 21:42, Philippe Mouawad wrote: Hello, For information: - https://blogs.apache.org/security/entry/cve-2021-44228 Regards On Tuesday, December 14, 2021, Philippe Mouawad < p.moua...@ubik-ingenierie.com> wrote: Hello, For me both 6.0 and 5.5 are ok. Regards On Tue, Dec 7, 2021 at 9:02 PM Milamber wrote: Hi, Currently, I prefer release 5.5 as version, add deprecated elements if needed. for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 (or why not 17) (so with OpenJDK official support instead Oracle Java). Using recent openjdk allow improvements from java release. and for 6.0, add support for HTTP/2.0 request seems be a requirement. Milamber On 07/12/2021 19:07, Felix Schumacher wrote: Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: I would be fine with both versions 5.5 and 6.0. Same for me. I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, so I would suggest releasing as 5.5, and going for 6.0 a bit later. I thought I could work on DSL this December, however, it turns out not to be the case. and more important a major version could be a good point to drop old stuff I am afraid it does not work that way. If we want to drop something, we need to announce the deprecation plan in advance. AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not deprecated), so there's no option to drop it yet. That is what I meant. If we want to use the next major version to drop things. 5.5 would be a good opportunity to mark those features as deprecated. so a 6.0 is not necessarily needed In 99% of the cases, the versions are there to convey the changes to the end-users. I really like realver: https://twitter.com/lorenc_dan/status/1209289792569131008 6.0 would mean "hey, there's something big, go and try it" :) That is true, too :) Felix Vladimir -- Cordialement Philippe M. Ubik-Ingenierie
Re: JMeter versions and release dates
Hello Milamber, If you're available, it would be good to release: - 5.4.2 with just the fix for Log4J - 5.5 (fix+improvements) If not, just 5.5 Thanks On Wed, Dec 15, 2021 at 9:02 AM Milamber wrote: > Hi, > > Probably need to release ASAP a fix version? 5.4.1? (from tag with just > the fix for Log4J) or new version 5.5 (fix+improvements)? > > Milamber > > On 14/12/2021 21:42, Philippe Mouawad wrote: > > Hello, > > For information: > > > > - https://blogs.apache.org/security/entry/cve-2021-44228 > > > > Regards > > On Tuesday, December 14, 2021, Philippe Mouawad < > > p.moua...@ubik-ingenierie.com> wrote: > > > >> Hello, > >> For me both 6.0 and 5.5 are ok. > >> Regards > >> > >> On Tue, Dec 7, 2021 at 9:02 PM Milamber wrote: > >> > >>> Hi, > >>> > >>> Currently, I prefer release 5.5 as version, add deprecated elements if > >>> needed. > >>> > >>> for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 > >>> (or why not 17) (so with OpenJDK official support instead Oracle Java). > >>> Using recent openjdk allow improvements from java release. > >>> > >>> and for 6.0, add support for HTTP/2.0 request seems be a requirement. > >>> > >>> Milamber > >>> > >>> On 07/12/2021 19:07, Felix Schumacher wrote: > Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: > >> I would be fine with both versions 5.5 and 6.0. > > Same for me. > > I am limited in time :-/, so I would not be able to rename 5.5 -> > 6.0, > > so I would suggest releasing as 5.5, and going for 6.0 a bit later. > > > > I thought I could work on DSL this December, however, it turns out > not > >>> to > > be the case. > > > >> and more important a major version could be a good point to drop old > >> stuff > > I am afraid it does not work that way. > > If we want to drop something, we need to announce the deprecation > plan > >>> in > > advance. > > AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not > > deprecated), so there's no option to drop it yet. > That is what I meant. If we want to use the next major version to drop > things. 5.5 would be a good opportunity to mark those features as > deprecated. > > > >> so a 6.0 is not necessarily needed > > In 99% of the cases, the versions are there to convey the changes to > >>> the > > end-users. > > I really like realver: > > https://twitter.com/lorenc_dan/status/1209289792569131008 > > > > 6.0 would mean "hey, there's something big, go and try it" :) > That is true, too :) > > Felix > > > Vladimir > > > >>> > >> -- > >> Cordialement > >> Philippe M. > >> Ubik-Ingenierie > >> > > > > -- Cordialement Philippe M. Ubik-Ingenierie
Re: JMeter versions and release dates
Hi, Probably need to release ASAP a fix version? 5.4.1? (from tag with just the fix for Log4J) or new version 5.5 (fix+improvements)? Milamber On 14/12/2021 21:42, Philippe Mouawad wrote: Hello, For information: - https://blogs.apache.org/security/entry/cve-2021-44228 Regards On Tuesday, December 14, 2021, Philippe Mouawad < p.moua...@ubik-ingenierie.com> wrote: Hello, For me both 6.0 and 5.5 are ok. Regards On Tue, Dec 7, 2021 at 9:02 PM Milamber wrote: Hi, Currently, I prefer release 5.5 as version, add deprecated elements if needed. for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 (or why not 17) (so with OpenJDK official support instead Oracle Java). Using recent openjdk allow improvements from java release. and for 6.0, add support for HTTP/2.0 request seems be a requirement. Milamber On 07/12/2021 19:07, Felix Schumacher wrote: Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: I would be fine with both versions 5.5 and 6.0. Same for me. I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, so I would suggest releasing as 5.5, and going for 6.0 a bit later. I thought I could work on DSL this December, however, it turns out not to be the case. and more important a major version could be a good point to drop old stuff I am afraid it does not work that way. If we want to drop something, we need to announce the deprecation plan in advance. AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not deprecated), so there's no option to drop it yet. That is what I meant. If we want to use the next major version to drop things. 5.5 would be a good opportunity to mark those features as deprecated. so a 6.0 is not necessarily needed In 99% of the cases, the versions are there to convey the changes to the end-users. I really like realver: https://twitter.com/lorenc_dan/status/1209289792569131008 6.0 would mean "hey, there's something big, go and try it" :) That is true, too :) Felix Vladimir -- Cordialement Philippe M. Ubik-Ingenierie
Re: JMeter versions and release dates
Hello, For information: - https://blogs.apache.org/security/entry/cve-2021-44228 Regards On Tuesday, December 14, 2021, Philippe Mouawad < p.moua...@ubik-ingenierie.com> wrote: > Hello, > For me both 6.0 and 5.5 are ok. > Regards > > On Tue, Dec 7, 2021 at 9:02 PM Milamber wrote: > >> Hi, >> >> Currently, I prefer release 5.5 as version, add deprecated elements if >> needed. >> >> for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 >> (or why not 17) (so with OpenJDK official support instead Oracle Java). >> Using recent openjdk allow improvements from java release. >> >> and for 6.0, add support for HTTP/2.0 request seems be a requirement. >> >> Milamber >> >> On 07/12/2021 19:07, Felix Schumacher wrote: >> > Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: >> >>> I would be fine with both versions 5.5 and 6.0. >> >> Same for me. >> >> I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, >> >> so I would suggest releasing as 5.5, and going for 6.0 a bit later. >> >> >> >> I thought I could work on DSL this December, however, it turns out not >> to >> >> be the case. >> >> >> >>> and more important a major version could be a good point to drop old >> >>> stuff >> >> I am afraid it does not work that way. >> >> If we want to drop something, we need to announce the deprecation plan >> in >> >> advance. >> >> AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not >> >> deprecated), so there's no option to drop it yet. >> > That is what I meant. If we want to use the next major version to drop >> > things. 5.5 would be a good opportunity to mark those features as >> > deprecated. >> > >> > >> >>> so a 6.0 is not necessarily needed >> >> In 99% of the cases, the versions are there to convey the changes to >> the >> >> end-users. >> >> I really like realver: >> >> https://twitter.com/lorenc_dan/status/1209289792569131008 >> >> >> >> 6.0 would mean "hey, there's something big, go and try it" :) >> > That is true, too :) >> > >> > Felix >> > >> >> Vladimir >> >> >> >> > > -- > Cordialement > Philippe M. > Ubik-Ingenierie > -- Cordialement Philippe M. Ubik-Ingenierie
Re: JMeter versions and release dates
Hello, For me both 6.0 and 5.5 are ok. Regards On Tue, Dec 7, 2021 at 9:02 PM Milamber wrote: > Hi, > > Currently, I prefer release 5.5 as version, add deprecated elements if > needed. > > for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 > (or why not 17) (so with OpenJDK official support instead Oracle Java). > Using recent openjdk allow improvements from java release. > > and for 6.0, add support for HTTP/2.0 request seems be a requirement. > > Milamber > > On 07/12/2021 19:07, Felix Schumacher wrote: > > Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: > >>> I would be fine with both versions 5.5 and 6.0. > >> Same for me. > >> I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, > >> so I would suggest releasing as 5.5, and going for 6.0 a bit later. > >> > >> I thought I could work on DSL this December, however, it turns out not > to > >> be the case. > >> > >>> and more important a major version could be a good point to drop old > >>> stuff > >> I am afraid it does not work that way. > >> If we want to drop something, we need to announce the deprecation plan > in > >> advance. > >> AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not > >> deprecated), so there's no option to drop it yet. > > That is what I meant. If we want to use the next major version to drop > > things. 5.5 would be a good opportunity to mark those features as > > deprecated. > > > > > >>> so a 6.0 is not necessarily needed > >> In 99% of the cases, the versions are there to convey the changes to the > >> end-users. > >> I really like realver: > >> https://twitter.com/lorenc_dan/status/1209289792569131008 > >> > >> 6.0 would mean "hey, there's something big, go and try it" :) > > That is true, too :) > > > > Felix > > > >> Vladimir > >> > > -- Cordialement Philippe M. Ubik-Ingenierie
Re: JMeter versions and release dates
>Are you planning on chaning the entire engine to use co-routines? It is not really that hard to switch the engine from threads to Kotlin coroutines: https://github.com/apache/jmeter/pull/540 The complicated part is to find a good HTTP client that can simulate lots of clients. For instance, last time I checked, Jetty HTTP client wanted 6 or so threads per "virtual client". >Is there any discussion about this where you can point me so I get more context? https://lists.apache.org/thread/sbwx4qylxkxxvbg1jw37jkd8gc29t5y7 >have you considered the advent of virtual threads to jvm and the implications > of coroutines to existing JMeter ecosystem (plugins and tools): https://openjdk.java.net/projects/loom/. Frankly speaking, it is not clear when Loom will be production-ready. On the other hand, Kotlin coroutines can already fulfill the need. Vladimir
Re: JMeter versions and release dates
Hello, What do you mean/intend with coroutine-based async samplers? Are you planning on chaning the entire engine to use co-routines? Are you planning to implement new samplers with this in mind? If such is the scenario, have you considered the advent of virtual threads to jvm and the implications of coroutines to existing JMeter ecosystem (plugins and tools): https://openjdk.java.net/projects/loom/. Is there any discussion about this where you can point me so I get more context? Thank you very much. Regards On 7 Dec 2021, 18:03 -0300, Vladimir Sitnikov , wrote: > So 6.0 is: > * http 2 > * with coroutine-based async samplers > * and programmatic test plan generation > * built with Java 17 > * distributed as jlink images > * with UI based on Compose Multiplatform > > It sounds cool, and the question is who implements all the features :) > > Frankly speaking, I see no reasons for deprecating features. > > Java 17 is not a problem for a standalone application, however, it might be > a problem for "jmeter as library" cases. > > Moving to 11 makes sense indeed. > > > openjdk > > OpenJDK is the source code. You can't launch openjdk unless you compile it > from sources. > You need to pick a vendor: SAP, Oracle, Azul, Bellsoft, Eclipse, and so on. > > Vladimir
Re: JMeter versions and release dates
@Milamber, do you think you could prepare JMeter 5.5 release? Vladimir
Re: JMeter versions and release dates
So 6.0 is: * http 2 * with coroutine-based async samplers * and programmatic test plan generation * built with Java 17 * distributed as jlink images * with UI based on Compose Multiplatform It sounds cool, and the question is who implements all the features :) Frankly speaking, I see no reasons for deprecating features. Java 17 is not a problem for a standalone application, however, it might be a problem for "jmeter as library" cases. Moving to 11 makes sense indeed. > openjdk OpenJDK is the source code. You can't launch openjdk unless you compile it from sources. You need to pick a vendor: SAP, Oracle, Azul, Bellsoft, Eclipse, and so on. Vladimir
Re: JMeter versions and release dates
Hi, Currently, I prefer release 5.5 as version, add deprecated elements if needed. for 6.0 version, probably we can migrate JMeter on next openjdk LTS 11 (or why not 17) (so with OpenJDK official support instead Oracle Java). Using recent openjdk allow improvements from java release. and for 6.0, add support for HTTP/2.0 request seems be a requirement. Milamber On 07/12/2021 19:07, Felix Schumacher wrote: Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: I would be fine with both versions 5.5 and 6.0. Same for me. I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, so I would suggest releasing as 5.5, and going for 6.0 a bit later. I thought I could work on DSL this December, however, it turns out not to be the case. and more important a major version could be a good point to drop old stuff I am afraid it does not work that way. If we want to drop something, we need to announce the deprecation plan in advance. AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not deprecated), so there's no option to drop it yet. That is what I meant. If we want to use the next major version to drop things. 5.5 would be a good opportunity to mark those features as deprecated. so a 6.0 is not necessarily needed In 99% of the cases, the versions are there to convey the changes to the end-users. I really like realver: https://twitter.com/lorenc_dan/status/1209289792569131008 6.0 would mean "hey, there's something big, go and try it" :) That is true, too :) Felix Vladimir
Re: JMeter versions and release dates
Am 07.12.21 um 18:48 schrieb Vladimir Sitnikov: >> I would be fine with both versions 5.5 and 6.0. > Same for me. > I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, > so I would suggest releasing as 5.5, and going for 6.0 a bit later. > > I thought I could work on DSL this December, however, it turns out not to > be the case. > >> and more important a major version could be a good point to drop old >> stuff > I am afraid it does not work that way. > If we want to drop something, we need to announce the deprecation plan in > advance. > AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not > deprecated), so there's no option to drop it yet. That is what I meant. If we want to use the next major version to drop things. 5.5 would be a good opportunity to mark those features as deprecated. > >> so a 6.0 is not necessarily needed > In 99% of the cases, the versions are there to convey the changes to the > end-users. > I really like realver: > https://twitter.com/lorenc_dan/status/1209289792569131008 > > 6.0 would mean "hey, there's something big, go and try it" :) That is true, too :) Felix > > Vladimir > OpenPGP_signature Description: OpenPGP digital signature
Re: JMeter versions and release dates
>I would be fine with both versions 5.5 and 6.0. Same for me. I am limited in time :-/, so I would not be able to rename 5.5 -> 6.0, so I would suggest releasing as 5.5, and going for 6.0 a bit later. I thought I could work on DSL this December, however, it turns out not to be the case. >and more important a major version could be a good point to drop old >stuff I am afraid it does not work that way. If we want to drop something, we need to announce the deprecation plan in advance. AFAIK MongoDB is not deprecated (at least, MongoScriptSampler is not deprecated), so there's no option to drop it yet. >so a 6.0 is not necessarily needed In 99% of the cases, the versions are there to convey the changes to the end-users. I really like realver: https://twitter.com/lorenc_dan/status/1209289792569131008 6.0 would mean "hey, there's something big, go and try it" :) Vladimir
Re: JMeter versions and release dates
I would be fine with both versions 5.5 and 6.0. For a 5.5 would speak two things. * Adding features can be done with a minor version update (so a 6.0 is not necessarily needed) * and more important a major version could be a good point to drop old stuff (mongodb sampler, which can't be used for modern mongodb servers, ftp sampler?, fill in your wishes, ...) But on the other hand a version is still a number, only. As asked on another thread, the more urging question would be, when and what do we want to release next ;) Felix Am 03.12.21 um 10:54 schrieb Vladimir Sitnikov: > Hi, > > Vincent suggested an interesting idea: release the upcoming version as > JMeter 6.0. > See > https://github.com/apache/jmeter/commit/417846471d320c5d18bfec899b8518276c8a9574#commitcomment-61294792 > WDYT? > > Initially, I did not think "a new component" might qualify for 5.x -> 6.0 > version change > However, now it looks like it might be a good idea: > * Open Model Thread Group introduces a new way to configure workload. > Of course, it is experimental, and it would sound fine when we refine it in > 6.1+ > * We add Kotlin language. Even though it is an "invisible" change for the > end-users (it is not much different from upgrading dependencies), > however, it might attract contributors. > * We increase distribution size (we bundle lets-plot for plots) > > I am not sure how long it would take for adding experimental DSL, however, > if we merge both DSL and OpenModel, > then it definitely qualifies as 6.0. > > Vladimir > OpenPGP_signature Description: OpenPGP digital signature
Re: JMeter versions and release dates
Ok for me On Fri, Dec 3, 2021 at 10:55 AM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Hi, > > Vincent suggested an interesting idea: release the upcoming version as > JMeter 6.0. > See > > https://github.com/apache/jmeter/commit/417846471d320c5d18bfec899b8518276c8a9574#commitcomment-61294792 > WDYT? > > Initially, I did not think "a new component" might qualify for 5.x -> 6.0 > version change > However, now it looks like it might be a good idea: > * Open Model Thread Group introduces a new way to configure workload. > Of course, it is experimental, and it would sound fine when we refine it in > 6.1+ > * We add Kotlin language. Even though it is an "invisible" change for the > end-users (it is not much different from upgrading dependencies), > however, it might attract contributors. > * We increase distribution size (we bundle lets-plot for plots) > > I am not sure how long it would take for adding experimental DSL, however, > if we merge both DSL and OpenModel, > then it definitely qualifies as 6.0. > > Vladimir > -- Cordialement. Philippe Mouawad.
