Re: Release JMeter 5.2 ?

Hello, I can try to do the next release with the new gradle build process (/ git), and update the release process wiki page with assistance of Vladimir. And in some weeks/months, probably I will go to a city near Philippe (in France, Tourcoing/Lille) so we can do a cross signing meeting betwe

Re: Release JMeter 5.2 ?

>Is there a procedure for gradle with the pre-requisites? You should have your PGP keys ready (and signed by at least one PMC). ^^^ we might want to organize a virtual signing party to meet each other and sign PGP keys. Then you have to gain some karma from milamber (I guess it is PMC chair who

Re: Release JMeter 5.2 ?

Hi Vladimir, I’ve never released version, usually it’s milamber Is there a procedure for gradle with the pre-requisites? If there is another volunteer I prefer not to do it, but if nobody volunteers I’ll try. Thanks On Tuesday, October 1, 2019, Vladimir Sitnikov wrote: > >Does anybody volunte

Re: Release JMeter 5.2 ?

+1 for me too Le mar. 1 oct. 2019 à 22:04, Vladimir Sitnikov a écrit : > >Does anybody volunteer to be a release manager? > > Just in case: I might try, however, I'm biased. > It might make sense if someone else would try first as it would surface > Gradle glitches. > > Vladimir >

Re: Release JMeter 5.2 ?

>Does anybody volunteer to be a release manager? Just in case: I might try, however, I'm biased. It might make sense if someone else would try first as it would surface Gradle glitches. Vladimir

Re: Release JMeter 5.2 ?

>Isn’t it time to release a new version? +1 Does anybody volunteer to be a release manager? Vladimir

Re: Release JMeter 5.2 ?

Am 1. Oktober 2019 18:04:57 MESZ schrieb Philippe Mouawad : >Hello, > >Isn’t it time to release a new version? > >Last version 5.1.1 is 7 months old. > >Current master has many enhancements and bugfixes that deserve a >release >IMO: >https://bz.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVE

ApacheCon North America 2020, project participation

Hi, folks, (Note: You're receiving this email because you're on the dev@ list for one or more Apache Software Foundation projects.) For ApacheCon North America 2019, we asked projects to participate in the creation of project/topic specific tracks. This was very successful, with about 15 projects

Release JMeter 5.2 ?

Hello, Isn’t it time to release a new version? Last version 5.1.1 is 7 months old. Current master has many enhancements and bugfixes that deserve a release IMO: https://bz.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVED&columnlist=product%2Cbug_severity%2Cassigned_to%2Cbug_status%2Cresolutio

Re: Git status update

>part of the release process >should become tagging the voted upon commit SHA under rel/ to make it >indelible. ('# git tag rel/v15.4.2 ' or something similar.) We have "publishRelase" Gradle task that creates "release tag" and moves the release from dev to release area on dist.apahce.org. We coul

Fwd: Git status update

[This was sent to private@jmeter, but does not seem to have been forwarded to the dev@ list.] Please note the penultimate paragraph about tagging successful releases under rel/ AFAICT, we have not been doing that. We should probably start doing this going forward. Note that the rel/ tags cannot

Re: Github: Delete v5_2_0_RC1

>Why not ? http://www.apache.org/legal/release-policy.html#publication >PUBLICATION >Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages. ^^ the above line is in bold right in r

Re: Github: Delete v5_2_0_RC1

On Tue, Oct 1, 2019 at 1:56 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Technically speaking users should not use GitHub. > Why not ? We could even put our binaries there, I'm pretty sure it would help extend exposure > > They should follow source releases only: > https://jmeter

Re: Github: Delete v5_2_0_RC1

Technically speaking users should not use GitHub. They should follow source releases only: https://jmeter.apache.org/download_jmeter.cgi Does it really cause confusion? I've removed the tag just in case. Vladimir

Re: CI vs GUI testing

Thanks On Tue, Oct 1, 2019 at 1:13 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Hi, > > I've enabled xvfb for both Travis and Jenkins, and it enables us to run > both headless=true and headless=false builds. > > Sample coverage improvement: > > https://codecov.io/gh/apache/jmeter/

Re: [apache/jmeter] Fix sonar security warning: False positive in the context of JMeter (8323941)

Why ? On Tuesday, October 1, 2019, Vladimir Sitnikov wrote: > Ah, I see this is "trust every host". > It looks like a bug to me rather than "nosonar". > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub >

CI vs GUI testing

Hi, I've enabled xvfb for both Travis and Jenkins, and it enables us to run both headless=true and headless=false builds. Sample coverage improvement: https://codecov.io/gh/apache/jmeter/branch/master/history/src/core/src/main/java/org/apache/jmeter/gui/HtmlReportUI.java?before=00fd8f09d578157cc9

Jenkins build is back to normal : JMeter-trunk #7438

See

Build failed in Jenkins: JMeter-trunk #7437

See Changes: [pmouawad] Fix sonar security warning: False positive in the context of JMeter [pmouawad] Bug 63793 - Fix unsecure XML Parsing [pmouawad] Add test for unsecure XML loading [pmouawad] Revert import ord