diff -u b/core/modules/update/lib/Drupal/update/Tests/UpdateTestBase.php b/core/modules/update/lib/Drupal/update/Tests/UpdateTestBase.php --- b/core/modules/update/lib/Drupal/update/Tests/UpdateTestBase.php +++ b/core/modules/update/lib/Drupal/update/Tests/UpdateTestBase.php @@ -7,15 +7,16 @@ * The overarching methodology of these tests is we need to compare a given * state of installed modules and themes (e.g., version, project grouping, * timestamps, etc) against a current state of what the release history XML - * files we fetch say is available. We have dummy XML files (in the 'tests' - * subdirectory) that describe various scenarios of what's available for - * different test projects, and we have dummy .info file data (specified via - * hook_system_info_alter() in the update_test helper module) describing what's - * currently installed. Each test case defines a set of projects to install, - * their current state (via the 'update_test_system_info' variable) and the - * desired available update data (via the 'update_test_xml_map' variable), and - * then performs a series of assertions that the report matches our expectations - * given the specific initial state and availability scenario. + * files we fetch say is available. We have dummy XML files (in the + * core/modules/update/tests directory) that describe various scenarios of + * what's available for different test projects, and we have dummy .info file + * data (specified via hook_system_info_alter() in the update_test helper + * module) describing what's currently installed. Each test case defines a set + * of projects to install, their current state (via the + * 'update_test_system_info' variable) and the desired available update data + * (via the 'update_test_xml_map' variable), and then performs a series of + * assertions that the report matches our expectations given the specific + * initial state and availability scenario. */ namespace Drupal\update\Tests; diff -u b/core/modules/update/update.compare.inc b/core/modules/update/update.compare.inc --- b/core/modules/update/update.compare.inc +++ b/core/modules/update/update.compare.inc @@ -383,8 +383,8 @@ * * Given a target major version, the available releases are scanned looking for * the specific release to recommend (avoiding beta releases and development - * snapshots if possible). For the target major version, it finds the highest - * patch level. If there is a release at that patch level with no extra ("beta", + * snapshots if possible). For the target major version, the highest patch level + * is found. If there is a release at that patch level with no extra ("beta", * etc.), then the release at that patch level with the most recent release date * is recommended. If every release at that patch level has extra (only betas), * then the latest release from the previous patch level is recommended. For @@ -399,15 +399,16 @@ * - 1.5 <-- recommended version because no 1.6 exists. * - 1.4 * - * It also looks for the latest release from the same major version, even a beta - * release, to display to the user as the "Latest version" option. Additionally, - * it finds the latest official release from any higher major versions that have - * been released to provide a set of "Also available" options. - * - * Finally, and most importantly, it keeps scanning the release history until it - * gets to the currently installed release, searching for anything marked as a - * security update. If any security updates have been found between the - * recommended release and the installed version, all of the releases that + * Also, the latest release from the same major version is looked for, even beta + * releases, to display to the user as the "Latest version" option. + * Additionally, the latest official release from any higher major versions that + * have been released is searched for to provide a set of "Also available" + * options. + * + * Finally, and most importantly, the release history continues to be scanned + * until the currently installed release is reached, searching for anything + * marked as a security update. If any security updates have been found between + * the recommended release and the installed version, all of the releases that * included a security fix are recorded so that the site administrator can be * warned their site is insecure, and links pointing to the release notes for * each security update can be included (which, in turn, will link to the diff -u b/core/modules/update/update.manager.inc b/core/modules/update/update.manager.inc --- b/core/modules/update/update.manager.inc +++ b/core/modules/update/update.manager.inc @@ -40,15 +40,15 @@ use Drupal\Core\FileTransfer\Local; /** - * @defgroup update_manager_update Update Manager: update + * @defgroup update_manager_update Update Manager module: update * @{ - * Update Manager for updating existing code. + * Update Manager module functionality for updating existing code. * * Provides a user interface to update existing code. */ /** - * Form constructor for the Update Manager update form. + * Form constructor for the update form of the Update Manager module. * * This presents a table with all projects that have available updates with * checkboxes to select which ones to upgrade. @@ -373,8 +373,8 @@ * This form is an intermediary step in the automated update workflow. It is * presented to the site administrator after all the required updates have been * downloaded and verified. The point of this page is to encourage the user to - * backup their site, gives them the opportunity to put the site offline, and - * then asks them to confirm that the update should continue. After this step, + * backup their site, give them the opportunity to put the site offline, and + * then ask them to confirm that the update should continue. After this step, * the user is redirected to authorize.php to enter their file transfer * credentials and attempt to complete the update. * @@ -474,15 +474,15 @@ */ /** - * @defgroup update_manager_install Update Manager: install + * @defgroup update_manager_install Update Manager module: install * @{ - * Update Manager for installing new code. + * Update Manager module functionality for installing new code. * * Provides a user interface to install new code. */ /** - * Form constructor for the Update Manager install form. + * Form constructor for the install form of the Update Manager module. * * This presents a place to enter a URL or upload an archive file to use to * install a new module or theme. @@ -746,9 +746,9 @@ */ /** - * @defgroup update_manager_file Update Manager: file management + * @defgroup update_manager_file Update Manager module: file management * @{ - * Update Manager file management functions. + * Update Manager module file management functions. * * These functions are used by the update manager to copy, extract, and verify * archive files.