Steve Ebersole,

I think key issue here is not simple lack of resources, but lack of back-compatibility with previous major version introduced consciously. Division of strategies was done in purpose, it's even been explained in official documentation, but what stopped you before introducing default, very simple implementation working for most simple cases at once, together with the change?

I can agree implementing physical strategy is definitely not a rocket science. However, it makes current situation even worse, because the very core functionality of your ORM was to translate between DB and code using convention-over-configuration approach with minimal amount of boilerplate stuff. Now it is impossible, thanks to decision about introducing breaking change to well known and liked library.