Upcoming Change to Privilege Secure Release Cadence and Versioning

We’re tightening up how we deliver updates for Netwrix Privilege Secure and Netwrix Privilege Secure for Discovery.

The goal is simple: predictable delivery of new capabilities, clearer versioning, and an easier time planning upgrades.

Want the full details? Click the link below!

Here’s what’s changing.

:date: Quarterly Feature Releases

Both products will now ship feature-bearing releases once per quarter. That means four major updates a year - no surprises, no shifting targets.

Hotfix releases will still ship between feature releases, but major functionality updates will align with this quarterly rhythm.

:1234: New Versioning Scheme: YY.MM.BUILD

We’re moving to a straightforward version format:
YY.MM.BUILD - Year, Month of Feature Release, Build Number

This gives you immediate clarity on when a release originated and where it sits relative to others.

How It Works

:compass: Quarterly Feature Release

  • The quarter is represented by the month of the release (03, 06, 09, 12).
  • BUILD is always 0 for a quarterly feature release.

Example:

  • The Q4 2025 feature release becomes 25.12.0.

:hammer_and_wrench: Hotfix Releases

Hotfixes increment the BUILD number until the next quarterly release.

Example sequence:

  • Initial Q4 2025 feature release: 25.12.0
  • First hotfix before the Q1 2026 release: 25.12.1
  • Second hotfix: 25.12.2

:tear_off_calendar: Next Quarterly Release

Once a new quarter’s feature release ships, we advance the YY.MM portion and reset BUILD to 0.

Example:

  • Q1 2026 feature release: 26.03.0
  • First hotfix after that: 26.03.1

:light_bulb: What This Means for You

  • Predictability: You’ll always know when major updates are coming.
  • Clarity: Version numbers tell you exactly when a release originated.
  • Smoother planning: Easier alignment of testing and change windows.
3 Likes