Me too.
However, Sparx requires users to raise a formal 'feature request' using a different part of the web site - otherwise these feature requests raised in the user fora appear to be disregarded.
Of course, if you do raise a formal feature request via the web site - your request disappears into a black hole and you hear no more about it.
This is not the case. You can post it here and file it as a feature request so Sparx does not loose track nor do we.
What do people think the new features in 7.5 are originating from? The Sparx crystal ball? 
Judging the numbers of users around the world and assuming the number of feature requests from those, it should be clear that not each of those will instantly make its way into the product.
I believe most of the requests do not fall into the "no way we never gonna do this" category but into a "sounds reasonable put it on the list" folder. Such a list is of course a prioritised one and the priority depends on the demand, effort, cost/benefit relation, etc.
Besides the fact that a priority might change from release to release and it bumps up and down the list 8-)
EA is not a project where you (mostly) get payed for features but a product and product lifecycle issues differ a lot from project business 
Oliver
You're absolutely right in everything you say, Oliver, of course. I know software development companies have "product roadmaps" that suggest the general direction that specific products are intended by the vendor to take over a period of say, two years or so.
And Sparx do demonstrate good relationships with their customers, and their customers very much reciprocate that positive relationship. I am a devout champion for Sparx EA.
And I don't expect Sparx to respond to every feature request with a personalised response saying "we are planning to implement your requested feature in Feb 2010, in release 7.6.4.
But. Where could we go with this topic?
Here's an idea.
I think it would be quite reasonable to expect Sparx to prepare a "Strategy for Product Direction" - where we - the loyal customer base - get to hear (possibly from the Sparx "Board of Directors" or "Steering Committee" or the Sparx "Product Strategist") some general statement of goals, and of what general features or capabilities Sparx perceive as being of greatest priority, and what features or aspects of the product they tend to view as being of lesserr priority.
And, of course, such a Strategy would be very high-level, notional, non-binding, indicative, ball-park, non-committal, for guidance only, your mileage may vary, if pain persists consult your doctor, etc.
Kind of like the IT Strategies that I assist my customers to write. Assisted in no small way by my use of this great tool called Sparx Enterprise Architect.
