You are here

development

Software has a changing nature; Drupal and its extensions are not the exception.
To be useful for a most of the users, those need to be on full releases, not only on the version control system; indeed the problem is not new and there is even a well-known phrase for one of its solutions: release early, release often
Therefore it is important to have a release plan.
Following after some context and reasoning, I propose a couple of practical guidelines on release schedule for contributed drupal extensions that I intend to use: release weekly until stable, then once a month following core shedule.

I have been writing about Drupal core statistics several times in the past, and incrementally, I have been automating the process of extract/sanitize contributors from commit messages and generating visualizations of the contributions.

The code is maintained on one of my drupal.org sandboxes, Drupal contribution analyzer, but I know, specially for the dependencies, that is not really trivial to run.

This time, instead of just presenting a new set of the statistics/visualizations output, I am glad to announce that I will be releasing a new version of the statistics and the visualizations once per week. In that way, the results will be available while I iterate on the code.

Since that time I was trying to improve it, and now I want to publish the new code(python prove me that it's rock solid faster :-p) and I also made some scripts to create lists of two interesting factors: activity by commits and by modified files. And, by the way, I generated tag clouds based on that info!