I am just leaving for one-week holidays, so I probably won’t follow up on what I’ll be saying here, but I do think the root of this "mishap" (so to speak) is precisely based :
1) On MODx’s release cycle : the dev team has a pace/release cycle that I have NEVER seen in any opensource projects (and I have belonged to a few communities, vital ones at that if you take Textpattern’s).
2) On the cutting-edge ideas which MODx is built upon : I really DO think MODx is groundbreaking in many ways, and it will be even more so in the future. That’s why lots of MODx users get enthusiastic when they discover MODx, and even more so when they dig into its full power. Then, at some point they encounter limitations and they just know those will be overcome by the team (more often than not, because the team answers pretty fast and communicates a lot about the future).
This undoubtedly leads to
high expectations.
May I say, in some rare cases,
unreasonnable expectations
Sometimes a given timeframe is set and has to be changed because the team has to adapt and take the best course of action : in this case, delaying a release. I think we can trust Ryan, Jason and Raymond to decide whatever is best for the project : they’ve showed time and again their dedication, talent and wits. You’ll have to trust that in this case, things are well thought out and you’ll probably be sorry having spoken too quickly when you do in fact see what’s in the release. Even better, you have to support them : that means contributing, which you’ve done, but donations sure could help too as Ryan puts it "Time may be against us, but so is work that keeps us able to contribute to this project." At some point you have to pay the bills, make a living. Let’s remember that MODx is a great gift to us developpers or webdesigners, a gift we have to be grateful for and to take care of