Minor-version release

Hello together,

After the patch-release of version 9.2.5, I was little bit wondering, because I rather expected the minor-version 9.3 to be published. The cadence of minor-versions (since 9.0) still is 6 months, right?

So here are my questions:

Is it planned from your netwrix-site, to have a minor-release in this current year?

If yes, when approximately?

Or is there a general time change in the release of minor-versions?

This topic points a little bit in the direction, whats mentioned in the release-notes of 9.2.5.

For a better planing and preparation “in the field”, in administrative terms of “updating”, it would be better to know more like a “roadmap” (a real simple one), minimum a month, better two months before a specific release / function is actualy comming / changing. Because that could avoid (sensless) multi-time updating or other “surprising” events, that just can`t be fixed from the administrators site in time, after the browser extension was updated automaticly to newer version at the users, e.g.

Thanks in advance

2 Likes

Hi Marcus - thanks for raising this, we know that release planning is an important topic!

To clarify: we don’t follow a fixed cadence for minor versions. Instead, we aim to deliver improvements and fixes as quickly as possible. That’s why you sometimes see some more ‘patch releases’, like 9.2.5.

Typically, bugfix and update releases are optional — if you’re not impacted by a specific issue, you don’t have to install them right away. Also, our Browser Extension is designed to be (even more) backward compatible - mainly because of the auto-updates a lot of users are receiving.

In this specific case, we decided to communicate a breaking change within just one minor cycle; however, this is not the regular process. Because of this exception, I’d like to share some more intel: yes, we are planning a minor release in the coming weeks. Stay tuned for more details — we’ll make sure you have the information you need to prepare in advance.

Cheers,
Sascha

1 Like

Hi Sascha,

Thanks for your response, it´s great to hear from you.

Ok, I understand.

So maybe thats only more like a “packing” -topic: In terms of which feature / bugfix comes in which release (patch /minor). That’s not really a difficulty for me at the “customer-site”, because I learned (also from other vendors), that the “update-politics” can change over time. So it´s all good.

See, apart from that, I got the perfect “live”-example - that went good, by the way – of what I meant in my initial query:

Thanks to the release notes of patch release “9.2.5”, for September the 25th(last thursday), I planed to update / upgrade of Password Secure, with all our internal (customer) approvals and change-processes, because of:

“The following Netwrix Password Secure Application Server versions are compatible with the Password Secure Browser Extension 9.2.5.33325:

Application Server: >=9.2.2.32693”

Beside of the client application (Windows App), we manual updated the server app to this version. And that was a fluke, because 1 hour later - no joke - the browser add-ons were automatically updated to version “9.2.6.”

Conclusion – this time:

We were lucky, not have waited for a “coming” minor update, because maybe we could have non-useable browser add-ons then (with the “old” version of the server app). At least, it was a risk of that, I think.

For the future:

I will have an eye (or two) for the requirements of the browser add-on concerning the demanded version of the server app.

That’s appropriate in our customer using scenario.

Cheers

Marcus

1 Like

This is great feedback Marcus!

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.