Traditionally, in a major open source project, lots of 'beta' and side projects are done off the main branches of the code, locally by developers 'scratching an itch' (like adding multiple variants). Kestas was smart to allow the hooks to add them so others could grow his code.
Now, to GET those side projects into the main branch, it usually goes through an entire process that usually includes:
- Code Format reviews (to make the code look uniform)
- Unit test and test coverage reviews (to prove that it is stable)
- A committee vote to determine if the new piece is desired in the next build.
- A long alpha and beta process to ensure that integration doesn't cause bugs to pop up
- Multiple release candidates to give the normal community a chance to try it and see if there are any troubles
- A major release is made and exposed to the public
So... yes, side projects and other 'cutting edge' stuff is out there and available, but it also can break or have other catastrophic errors (like loss of user info, cheating, etc...). I'm not suggesting that the other developers code is garbage, just the nature of the beast. Kestas is playing the role of the code owner and is forced to wait until everything is stable before releasing. This is why the community here is the largest. It was the first ones, and know the code remains as stable as possible.
Hope that explanation helps. :)