What is the point of having Automatic Updates Extensions be a separate module?
Originally, I think the idea was that we wanted to develop it in its own experimental scope, because Automatic Updates was still under heavy development. But that situation is longer the case; both modules are stable, and the division between them causes needless complexity and UI confusion.
Merge Automatic Updates Extensions' functionality into Automatic Updates, and mark the sub-module.
If you have Automatic Updates Extensions installed: Uninstall it at your earliest convenience.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
phenaproximaComment #4
phenaproximaI discussed this with @tedbow over Zoom, and he blessed this idea.
Additionally, it seems at this point that Automatic Updates is not likely to go into core in its current form; if we did, it would be renamed ("Update Manager" seems to be the preferred nomenclature) and probably heavily refactored. That's okay; Automatic Updates is a critical dependency of Drupal CMS, which is the default download of Drupal, and this change does not affect its strategic importance. Consolidating its functionality into one module is the right way to go.
With all that in mind, merging this chungus. It's possible that not all tests will pass, but it seems that some of the build tests are a little flaky, because there is no god and Satan is dancing on my disk drive. I don't have time to rewrite the build tests right now (although they need it).
Comment #6
phenaproximaMerged into 4.x.