Hi Vladimir and all, I agree with waiting two weeks to include the infrastructure for PR 6389 in the 6.0 release.
Additionally, I have been following your work on the pgjdbc documentation. I believe we should consider a similar restructuring for the JMeter documentation as well. Antonio Gomes Rodrigues Le mer. 20 mai 2026 à 22:25, Vladimir Sitnikov <[email protected]> a écrit : > Hi Felix, Antonio, all, > > Sorry for the slow response. Here's a quick status update. > > PR 6389 / the "explicitly unset" gutter work: I estimate one to two more > weeks to get the current branch > (gutter pattern) into reviewable shape. > > Past that, extending the new UX to every relevant field can be incremental > follow-up PRs. > So we have a choice: wait the two weeks and include the infrastructure in > 6.0, or cut 6.0 now and land it in a follow-up. Either works for me; > opinions welcome. > > On "can anyone help out": yes. Separately from this thread, Shane Evans > (BlazeMeter / Perforce) reached out about dedicating engineering resources > to the project. > Their concrete pain is merged-but-unreleased dependency/security fixes > blocking their customers (the Tika PRs #6556 and #6579 were the examples). > I've put him in touch with Milamber over email. Useful places their > bandwidth could plug in: > - reviewer/tester capacity on open 6.0-scoped PRs > - testing release candidates (vote with results) when 6.0 RC is cut > - regressions reported against nightlies > > I'll follow up separately on PR 6661 (oro default), 6610, and the > rhino-engine question. > > Vladimir >
