I just finished a stint as commitfest manager for the September (2023-09) commitfest of the PostgreSQL project. After the conclusion, I of course looked at the statistics and saw that 68 patches had been committed, which I felt was low. But then I looked a bit into the past and noticed an interesting pattern: Since the beginning of the current five-commitfest system, the September commitfest almost always has the lowest number of commits.
Consider the number of patches with status “Committed” after each commitfest:
Here is a similar statistic directly from the Git repository: The number of commits per month, over the last five years, which covers approximately the same time interval as above.
$ git log --since='2018-10-01' --until='2023-10-01' --format='%ad' --date='format:%m' master | sort | uniq -c 953 01 819 02 1395 03 1258 04 853 05 738 06 1052 07 864 08 922 09 771 10 949 11 701 12
You can see here that the commitfest months (01, 03, 07, 09, 11) have higher numbers than their neighboring months, and among those commitfest months, September has the lowest number.
I don’t quite understand the reasons for this. Intuitively, you could make arguments why some of the other times of the year should see lower activity (holidays? vacation?). But in any case, it is good to keep this in mind when assessing commitfest throughput. Looking at the numbers in the PG17 cycle so far, even though they are much lower than the 2023-03 commitfest, we can expect that PG17 will have more activity in total than previous development cycles.