communication

Luminis upgrades/patches - best practices for documentation/communication

Hi,
I'm curious about what other schools do for documenting and communicating changes to end users, as a result of Luminis upgrades and patches. Are there any standards or best practices for the same? Do you just use the release notes or document changes in a more user friendly way?

Any input/suggestions will be greatly appreciated.

Thanks,
Shyam

Syndicate content