## Description of problem:
Two main config files define the statistics: modules and releases. For each
module added/altered, its respective entry in releases should change. This
forth-and-back process causes mistakes (a module not showing up in a release etc).
To fix it we can create a new page with a big table showing on the releases as
columns and modules as rows, and identify which module is active in which
release with which branch.
(willing to help out anyone who would like to tackle this)
Basically it's this page:
containing modules instead of languages:
With a 'tick' in the cell if that module is 'active' in the particular release.
Data are drawn (classes to extract them are already there) from: