Fully agree. Today’s 2338 also says :
“Update widget to latest”
But no idea what went into 2332 and 2338. We need a nice list published once again in the Widgets subforum.
We’re still having issues with the pickerWheel on graphicsCompatibility 1… It barely works. I’d provide a test and everything but just create a pickerWheel and use graphicsCompatibility 1 and you’ll see that it barely works. The scrolling doesn’t stop at one particular point, and if you scroll up and down etc you don’t always get the correct choice. Why is it like this after almost 1,5 years after the widget release.
FYI Corona Staff, we are STILL using the 1.0 widgets for all our components because the 2.0 ones are still insanely unstable, 1,5 years AFTER the official release. Beebe cooked up the older 1.0 widgets in just a few months which you were ‘ashamed’ of. I’d say it’s the other way around by now… (Nothing personal to the people working on the widgets) but come on Corona, 1.5 years and the widgets STILL don’t even emulate the older ones…
Edit: I attached a video demonstrating how the pickerWheel works in a different thread, link: http://forums.coronalabs.com/topic/37217-list-of-open-widget-20-bugs-promised-features/?p=252643
I fully agree with your sentiments on the time it has taken to resolve these issues. 1.5 years to get something stable, which originally was released because Widgets 1, in Walter’s words, was “embarrassing” is simply double-embarrassing. However, it is what it is and the only choice clearly left to us to consider is to move on and not use Corona SDK at all. With all the lobbying and complaining this is the best we got.
I think the Widgets 2 is now stable enough to consider (at least for me) but the problem here is probably the G1 compatibility mode. I saw on day 1 that this mode would not be well supported and issues fixed in G2 native mode would not necessarily be fixed in G1 mode simply because not as many people are using it and reporting bugs etc. Moving on from G1 compatibility mode will make a big improvement on your Widgets 2 experience. Highly recommended.
Good luck with your project.
Unfortunately we have not been able to do so for other various reasons. Until we find a good solution for our group-nesting problem which we reported a few months ago and others have had the same issue, this thread: http://forums.coronalabs.com/topic/46954-solution-to-fix-nested-groups-in-g20/ we wont be able to fully migrate properly since our apps are still heavily depended on the old previous group G1.0 behaviors. But thanks for the tip nevertheless 
I know exactly where you are. Been there a few times where I needed to go forward to ‘enjoy’ some fixes to some components but could not due to other bugs or issues introduced along the way. Very tough place to be especially when you have deadlines to deal with as well. IMHO, the whole post G2 stabilization era is not over yet. Almost a year over that and we are still dealing with the massive transition G1 to G2 proved to be. The upcoming changes, ie Windows Phone support etc scare me even more. Lets hope for the best.