Change process to release security patches
whenever Osisoft identifies security issues on PI / PI AF, they deliver fixes through the next release of these applications.
This is not convenient as upgrading to a new release is a risk that we don't like to be forced to take and has a cost (we manage about 40 PI servers WW under different versions).
We would rather appreciate to have patches applicable to our versions of PI. This is what software vendors usually do.
Could you please consider managing your future security patches this way?
Roger Palmen commented
I'm not yet seeing how this helps in keeping the cost down. In all cases you have to test before deployment to stay in control, if it is a version upgrade or just a security patch.
I do agree that new versions include new functionality and could break existing functionality (seldom, but it does happen). So there is some merit in that