A release plan for contributed drupal extensions

tl;dr: Review the plan at the end directly.

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.

Re-activating Vote Up/Down

Vote Up/Down is a drupal module that uses Voting API to provide a way to vote.
These notes are about part of the history of the module, and the recent news about it, including a couple of releases!

On why cron.d file was not running

If neither the --lsbsysinit option nor the --regex option is given then the names must consist entirely of ASCII upper- and lower-case letters, ASCII digits, ASCII underscores, and ASCII minus-hyphens [run-parts(8)].

And that's is why the cron.d file was not running!

Gladly someone mentioned it before.