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
