If you read some of the development responses in the APEX 3.0 Feedback application
[…] I have logged a bug but it won’t be fixed for 3.0 because we have already sent our translations out and even though this would not be a new string […]
it really looks like that they are coming into a state where they don’t do any fundamental changes anymore.
But I’m sure the APEX development is happy if you help them find bugs in the new features so that APEX 3.0 is a really stable development environment when it gets released. Or as Carl would say it
I’m sure he’d be thrilled to get bug reports and feature requests who doesn’t want more work?
So get your b… up, logon to the evaluation instance of APEX 3.0 and do a shake down test of the new features! Together we can help them to create a stable new release with a lot of nice new features!
For all the existing testers, to my knowledge the evaluation instance has been refreshed on Feb. 20. So check out what has already been fixed!