Improved behavior for update Drupal 8 Core

At first we want to thank you Tatár Balázs János (European Commission) and Anja Schirwinski (undpaul) for reporting the issue and discussions about the new feature.

Initially, the development of Drop Guard was done for Drupal 7, which has a sequential version numbering system: 7.10 .. 7.20 .. 7.50. If a user uses 7.50 and 7.51 is available he should apply this update and almost certainly this update will be applied without any problems.

Drupal 8 supports several parallel "active branches", right now it is 8.5, 8.6 and 8.7.

Feature close-up: Time schedule of actions

A successful day can be interrupted uncomfortably by recently released updates. Some of us process updates immediately, others wait for their client’s or manager’s feedback and some teams schedule them regularly on a specific day. So, when it comes to update automation with Drop Guard, our users should be able to apply their current schedule workflow as well.
To cover these individual schedule needs, we provide the “Time schedule of actions” feature on the “Events” tab of your project’s config setting site.
Within this post, you will learn how to benefit from this feature.