The features I listed were just examples, and only a couple that have been publically announced to be on the DNN road map.  I didn't at all imply that they were the only ones.  You are taking these statements too literally.  Fortunately, you have mentioned a couple more upcoming features (content versioning/workflow, and multilanguage support/complete localization).

I still think you are missing the point.  You are only thinking in terms of your customers, while the focus of the DNN Corp must be much more broad.  In many, many ways, we are all their customers.  They have to satisfy the needs of the developers, hobbyists, extension vendors (modules, skins, etc.), user groups, community members, core team members, project team members, small businesses on the platform, medium businesses on the platform, large businesses on the platform, and so on...

What would you suggest be the solution to fairly support all of these stakeholders on the DNN platform?  At this point, I am not sure you are providing the community with constructive feedback.  

DotNetNuke Community and Professional Editions will be developed / tested / released in parallel. DotNetNuke Professional Edition is actually built on top of DotNetNuke Community Edition - so that vast majority of enhancements, bug fixes, and testing will actually be on Community Edition. There will also be some extra functionality in Professional Edition - features which would not be applicable to the majority of users, but which are important for more serious business users.

A module compiled against DotNetNuke Community Edition 5.0 will work with DotNetNuke Professional Edition 5.0 and vice versa ( ie. module developers will be targeting a specific framework version - not a specific product edition ). We intend to preserve binary compatibility between the two editions, as it is essential for the preservation and health of the ecosystem.

One of the benefits of having a "supported" Professional Edition is that we get much broader feedback and insight into real world scenarios. One of the problems we have experienced in the past is that many systems integrators help customers install and configure DotNetNuke but fail to report issues back to us. There are many reasons for this including privacy, customer confidentiality, concern about losing credibility with the customer, loss of competitive advantage, resource constraints, etc... but the bottom line is that it does not help us or the community.

With the introduction of the SLA program we were amazed at the types of problems being reported, and greatly appreciated the ability to directly interact with production environment so that we could diagnose and solve the source of the problem in the core framework itself. In fact, some of the more high profile, complicated bugs fixed in recent DotNetNuke releases are a direct result of our SLA program and certainly would not have been fixed had it not been for this customer interaction.

As far as concern raised about resources and focus, the fact that DNN Corp is finally 100% focussed on product development should result in major improvements in the platform. The support which we do for the platform results in bugs being fixed and critical enhancements being escalated in priority which ultimately end up in the product sooner and with more testing. In the past, because we had to find ways to feed our families, we often got sidetracked doing consulting projects for clients - which really distracted our focus away from the core product. The new product should ensure our focus is where it belongs.

First of all, I am happy that Shaun's post seems to have addressed your concerns.

However, I would like to point out that I am practicing what I have asked of you.  I did not just say something like, "I don't like what you're saying."  I have challenged you to not only tell us about why something is bad or that you simply have a problem with something.  But in situations like these, also provide constructive feedback to tell everyone what would make you feel better about the problem.  In other words, something like this:

"You know Core Team, I don't know why you chose to go forward with item X.  I would much rather have seen solution Y, and here's why." [solution details would follow]

This would better facilitate a conversation that becomes both informative, and yet have constructive feedback and public discourse that would in the end benefit the entire community in a positive way.  I am not purposely criticizing you like you might think and feel.  I am trying to help us all to communicate our problems and solutions better.  I am sorry if you feel otherwise.

You catch more flies with honey...  http://www.threeriversinstitute.org/AppreciatingYourWayToXP.htm