<p>Please, don't add anything else to 2.0, it's an easy way to endup with a beta cycle that takes forever and a week (I worked over 20 years in IT, over 10 of that as a programmer, the just one more change is what kills development schedules, because the bugs become a moving target). You folks on the development team should have implemented a "feature freeze" at the start of the beta cycle, and put all our suggestions in the hat until 2.0 is out the door, and then dig them out for 2.2. </p><p>Speaking of such, any idea when we might see RC1????</p><p> </p><p> </p>