Hello, For me both 6.0 and 5.5 are ok. Regards On Tue, Dec 7, 2021 at 9:02 PM Milamber <milam...@apache.org> 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
