Good analysis. The problem is that trunk has not (or had not before include) enough distinguishing features to make it really appealing compared to 2.1. And it therefore doesn't urge us to release it, leading new features to be added to 2.1 also as we need them on production systems. Chicken and egg...
So raising the demand for 2.2 may simply be a matter for us developpers to add new features only on 2.2 and use it more on realworld projects. That will urge us to officially release it before our projects go into production.
My personal opinion is that we just need these virtual components and then have the final 2.2 (apart from polishing). Everything else can go into 2.3.
Carsten
