Where is the best place for legitimate information?

Thanks for the timely input and you are right...there is a lot of room for improvement. The biggest frustration with Microsoft's Cloud First release strategy is in the perception that they seem to think this gives them the leeway to release substandard product without adequate QA. I see so many more obvious bugs in their releases under this strategy. For instance, with a modern library performing in place records management the Checked Out Icon appears instead of the Lock Icon for locked records. Doesn't this seem like basic QA? When you upload a document into a Modern library the circle is not available to the left of the document until the page is manually refreshed. Once again, basic QA. I could rattle off at least a couple of handfuls of issues like this that we still see and these libraries have been released for how long? The worse thing is I have not seen these reported anywhere else except in this forum.

How am I as a user supposed to transition to a product where I have no idea what awaits me. I transition and step on landmines left and right and that is acceptable? Who is maintaining a bug list that I can review to make the determination to move to the new feature?

As far as your question regarding the classic experience, my company can stay on the classic experience and we may just do that. The push for moving to the new experience is to actually try to compensate for inadequacies in the classic Office 365 experience. For instance, our users have a big problem with documents syncing in OneDrives and SP Team Site libraries because of the obvious problems with the Onedrive client. I would love to force them to a Web Only approach but I can't because classic libraries don't accomodate drag and drop libraries whereas the Modern ones do. I can't tell my users to upload one document at a time, recreate folder structures manually, or stop everything so that we can strategize an appropriate metadata layout for the library. The new client that we have been waiting for is finally out in preview after a year and is still having problems so I'm a little stuck there. We would also like to have people use groups more since Microsoft is really pushing them, they offer direct linking from Outlook, interface with Planner, and incorporate conversations but we can't because we need to be able to have multiple libraries in Groups. The new Groups support that but I can't turn on new Group functionality in the Classic Experience and I'm not sure I want to risk turning on the new experience and disabling it individually at the list level (Site Contents would be Modern and I can't do anything about that). There are a couple of other reasons we are looking to get away from Classic but really can't....AND we really have no single full Sharepoint solution that works. Looks like I will probably end up staying on Classic and putting a link on our user's OneDrive page to "Open in Explorer".