Tuesday will be the 24th stable monthly release of Parrot in a row.
If your goal is releasing once a month, that is a fine record.
Please note. I have absolutely no qualms in saying that you joining/leading the Parrot project not just made it better, but saved it.
But I strongly suspect that a knowledgable, labels-shy observer with a good view of the project, and a good knowledge of you, would attribute the good and steady progress it has made since your involvement, down to your personality and drive and programming skills; not the currently trendy label, set of checklists or headline statistics for what at its crux, amounts to no more than having a well-thought through set of development procedures. And using them.
Getting back to that quoted statistic. I'm too far away to know, but you might like to consider, how much time & effort (yours and others) is expended on a monthly basis producing those monthly releases--and keeping up with (downloading, exploring, familiarising, etc) them?
And would the project be enhanced or diminished had 50% of that effort been expended on actual development, by having bi-monthly releases instead?
In reply to Re^4: Some reflections on the Brainbench Perl Test
by BrowserUk
in thread Some reflections on the Brainbench Perl Test
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |