Drilling-Billy
Did you explain to your boss that Flarum is open source, working without funding, no full time developers and a fairly small core team as topping. And that those have 100% jobs and or studies?
Based on the above, it is completely understandable that Flarum takes some time between builds.
I am absolutely certain that once the API is finalized, and the core is stable, the whole environment with extensions, 3rd-party companies, services and more will increase dramatically, and development speed will increase automatically due to more contributors with vested interests (Those companies/service providors), and generally more users. (There are several large communities waiting to switch over in a release or two).
A brief, quick and dirty comparison:
#Wordpress.
Wordpress currently have roughly 23 core team members.
Additionally, there are hundreds of core contributors contributing toward each release.
One of the main reason behind all those contributors is companies and service providers, plugin creators and theme designers having vested interest in keeping wordpress fresh and dandy, else their whole business model dies.
All this leads to Wordpress being able to push several releases a year.
However, look at it's early days. Between 2.0 and 2.1 there is two years (!)
It is also safe to assume that the reason the first few releases was so rapid, is because wordpress was a fork from an already functional CMS(blog engine/whatever).
TL;DR: Read the first few lines, drop the comparison section.
