Read on Twitter
Looking at @deno_land software development analytics with @cauldronio: on the importance of release announcements. Also: why opening issues on Tuesday? Thread 
Today I was having a look at the stats that @cauldronio had backed for me on @deno_land https://cauldron.io/dashboard/1341?from_date=2017-07-27&to_date=2020-07-27 Since 1.0 was released on May 13th, I have been keeping an eye on it. Numbers are impressive for a (relatively) new project (these figures are for last 6 months)
The effect of the release announcement of @deno_land 1.0 is huge. But it cannot be said it was *due* to the release: see the increase in activity during the last weeks of April, first weeks of May (charts show the whole story of the project, ~3 years) https://cauldron.io/dashboard/1341?from_date=2017-07-27&to_date=2020-07-27
The effect is more apparent if visualized for the data of the last year. Remember, 1.0 of @deno_land happened on mid-May. But you can spot a clear increase in commits since late April. New issues and pull requests, however, increase only during/after the release
In summary, @deno_land developers were preparing for the release with a clear increase in activity, but after it, they attracted *a lot* of new issues and pull requests. How well did they cope with them, and for how long lasted this impulse?
Six weeks after the announcement (late-June) commits were back to normal (~130 commits/week). But look at the chart on the right: those are authors per day. From 5-10 before the release, by late-June they had 10-20. A good signal of external engagement.
Peak for authorship is May 15th https://cauldron.io/dashboard/1341/public-kibana Clearly related to the 1.0 announcement. But also to a very quick reaction to external contributions by @deno_land developers. Look how well closing pull requests fit opening them (data is per week) New code came in quickly!
A lot of attention was also devoted to issues, but @deno_land developers couldn't close issues as quckly they closed prs (chart is issues per week). That's normal: many issues need time to be dealt with. In mid-June, closed and open issues were again balanced.
