• 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!
  • 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.

Changelog

matt.simpson

Basic Pleskian
I'm going to bring this up again, because it is not only important, but imperative that administrators' know exactly what has changed in a Plesk release.

I just installed Plesk 8.2 fresh install yesterday, and at the end of the day there was an update available.

Trying to find out what changed from the morning to the afternoon is nearly impossible.

Upon looking at what packages it downloaded I found:

psa-hotfix3 8.2.0 rhel4.build82070807.17i586
psa-locale-base-en-US 8.2.0 rhel4.build82070807.17noarch
psa-qmail 1.03 rhel4.build82070807.17i586
psa-selinux 8.2.0 rhel4.build82070807.17noarch
psa-updates 8.2.0 rhel4.build82070807.17noarch

Fair enough, but:

1. Okay, but what does this hotfix3 actually fix.

2. What changed in the language files.

3. What changed in the qmail configuration.

4. Did it fix the problems I was previously experiencing with selinux.

5. What is psa-updates, how much more generic can you get.

The changelog in the Downloads section used to be useful, now it's full of advertising half-wit BSYT speak instead of useful information.

Instead of calling that a changelog, how about calling that changelog-overview, and keeping the changelog as a real changelog.

Best Regards,
~Matt Simpson
 
Back
Top