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.
The overview of Drop Guard changes in January:
- Decreased loading time for pages
- Fixed a problem with determining of packages with sub-modules
- Removed the PHP 5.6 executor
... and a lot of other points. Read more in this post.
A tool only performs as good as it’s configured and handled.
This post gives detailed insights into the important touch points of the Drop Guard actions you need to configure in order to benefit from a smooth and individual update pipeline.
It has been a week full of impressions, old and new friends and exciting challenges at Drupal Europe! The Drop Guard team members Joe, Max, Alexey, and Johanna attended the Drupal event from 10th to 14th of September.
This is a brief overview of our Drupal Europe highlights and impressions, enjoy it!
Our CTO Max Madl held his first workshop at Drupal Europe last week. The main goal of this hands-on session was to show the audience what it means to update a Drupal project
b.) with helping tools & services
c.) fully automated.
This post provides you the gateways to the session slides "Drupal Europe 2018: Hackers automate but the Drupal community still downloads modules from drupal.org" and the topics update automation and Auto Update Initiative in Drupal.
I’ve joined the Drupal mentoring team for the first time last week at Drupal Europe.
In this post, I’ll share how and why this contribution changed the way I think about Drupal events and the Drupal Community.
Win a free Drop Guard update package!
We are excited! We want to share with you:
There will be a huge European Drupal Event next week and we will attend - what do we bring to the table?
It’s in our hometown Darmstadt, right on the doorstep - where can you spend your free time?
We’ll volunteer actively for the first time - join the contribution squad!
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.