• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Update notes not in release notes

matt.simpson

Basic Pleskian
Hello Parallels,

Can you do me a kindness? Please do not release micro updates without adding some sort of documentation to your release notes section. The documentation should be done before the MU is available for download so people know what "important" security updates they are / have applied. I've noticed this happening with a good number of the 11.0.9 micro updates (#16 being the latest).

While we're on the topic, change log entries like "Major security enhancements." in #13 really needs to be elaborated on IMO. You don't need to go into specifics, but at least give us a clue what you're changing before we apply an update.

2c,
-Matt Simpson
 
Please do not release micro updates without adding some sort of documentation to your release notes section. The documentation should be done before the MU is available for download so people know what "important" security updates they are / have applied. I've noticed this happening with a good number of the 11.0.9 micro updates (#16 being the latest).

If you have enabled manual mode of MU installation it doesn't matter when we publish notification because you can wait and read announcement and then make decision of installing or not installing this MU.
If you have enabled automatic mode of MU installation it doesn't matter as well because MU will be applied despite fact when you read announcement.

While we're on the topic, change log entries like "Major security enhancements." in #13 really needs to be elaborated on IMO. You don't need to go into specifics, but at least give us a clue what you're changing before we apply an update.

When we fix well known security issue we publish corresponding CVE. When we fix security issue which was found with help of internal audit we can't provide any information because it is security question and we do not want to give any hint to intruders. But we provide indicator for customers - Minor, Major or Critical security update. I think it is enough for most customers for making decision about importance of this security MU.
 
Back
Top