Our Blog

What does it take to be up2 date?

Asparuh Krastev
by Asparuh Krastev on Thu 24 April 2014 No comments

OK, so your new Drupal website was just launched. It went through all the phases of specification, construction and acceptance. It has finally been launched. Now you can sit back, relax, watch the traffic flow and the rankings increase.

Don’t get too comfortable though. With all the effort you dedicated, you probably put one thing in the background. And that is – regular updates. Have you ever wonder what does it take for your website to be up to date?

It is wise to keep that in mind. After the website construction, you are already behind with the updates, that were released while the project was active. Not to mention if your website was released around January 2011, when there was a peak in the commits. That is 53 updates in one month, based on a common set of modules.

In the following survey I took a list of 130 commonly used Drupal modules and queried their repositories for all tags that have been created, using a simple bash script:

for i in $(find . -maxdepth 1 -type d) ; do
  path=${i}
  folder=$(basename $path)
  git --git-dir=$path/.git fetch
  git --git-dir=$path/.git log \
    --tags \
    --simplify-by-decoration \
    --pretty="format:%d;%at;$folder%n" | \
    grep ^\ \(7.
done

Note: The script must be executed in a folder, containing the cloned module repos.

The repository tags represent the versions, which appear in the modules’ download page. The following diagram shows the number of updates per month since Sep 2008:

Versions chart

The peak month was Jan 2011 – 53 updates. On average there were 30 updates per month between August 2010 and November 2012. At this moment updates are still reported at the rate of around 12 per month. One should consider this fact when planning for a new Drupal website.

Asparuh KrastevWhat does it take to be up2 date?

Related Posts

Take a look at these posts

Join the conversation