Nope, version 1 is great, and will run just fine for a year on the site. Feature improvements are welcome (see smaller feature suggestions forum) and I am sure 1.1 and up is to be expected this year. So patiently waiting is what I am doing. I don't "need" anything at this point. Majority is there, and runs very well.
Don't fix what is not broken.
If you have a release and they roll out maintenance releases weekly, you can just skip the ones minus the security updates. And wait until 1.1 is out.
I would not mind to auto upgrade monthly to improve performance, stability, get more completed features and options, and improve usability. You can customize the product without touching the source code and without touching the style. So upgrading is a 2 minute job, if at all.
I am not dying.. dying.. I would like a new version, but 1.0 is so awesome I am taking my time to enjoy, and savor it. Like a really really good piece of a gourmet meal that I just have to taste every bit.
Also, XenForo should take a page from the IB book about small releases:
1) Customers get annoyed because they have to upgrade, and they don't like to upgrade frequently (no time)
2) Modders get annoyed because they have to review their mods, yet again, for the new version. Next time I have to answer "does this run in x.y.z", I am going to cry
3) Templaters get annoyed because they have to update their styles. If things break, it's worse
4) IF (if), there are no major features, or features that make sense, you might not upgrade, but still you are left with that weird feeling of .. "but I am not in the latest version" in combination with "but several bugs were fixed"
5) The more versions out there, the more "fun" for support, that now has to ask "what version are you in", and old bugs keep getting reported because customer refuses to upgrade to the version in which his bug is fixed
So.. bottom thing is, frequent releases are broken and just don't work well for THIS particular software scenario. They are so damn annoying I am not sure they are even worth it. Of course, you might get the features "earlier", but I have yet to so a single feature that I cannot absolutely wait a month or two for.
I would be fine with a 3 releases per year schedule (or 2)
Please note that does not by any means mean "abandon us". Please come by every month and talk about a new feature you just implemented and is confirmed, and will make it, and will be in the next release ... (with screenshots, preferably)
I'll be happy if the devs take their time and continue to build upon a product which has proven very stable and innovative. This will take them longer than the pre-gold 2 week incremental releases/updates and I would expect releases/updates to take significantly longer which I am happy to wait for. The devs should take they're time, enjoy what your doing and everything will fall into place and at the end of it we will all have more features and a continued solid product.
I'd expect with the open and now fixed bugs we see a maintenance release (1.0.1 or whatever) in the next month or so. Would be nice to see even on a superficial level to see regular updates early on to build confidence in the product.
Why should there be set releases at all? Some features will take longer than others to complete, and releases should be released only when there are new features (When they reach a milestone) or when there is a security fix, or a large number of bug fixes.