Chris McNulty I hope you understand that quotes like these scares the crap out of people
"Further customization options are dependent on the release of the SharePoint Framework by year end. In the interim, classic mode remains fully supported."
First, we need to wait to the end of the year before the SharePoint framework is released. That isn't a big surprise. But then you mention, as long as it's not released classic mode is fully supported.
So when it's released you need to make sure you rebuild your solutions to work with the the new ui and framework asap, else you're in trouble.
I'm really looking forward to a quote from Microsoft where they state the minimal timeline where classic mode will be supported. Something like: We support classic mode to end 2020 and after that we look inti usage data to determine if we can phase out the classic model. Now we constantly hear and sometimes interpret: we will kill classic mode as soon as we can, and it's going to be in 2017 not later.
That's a really tough message for our customers. A scope of less than a year to rewrite all customizations.
I've created a seperate topic to address these concerns: https://network.office.com/t5/SharePoint-Developer/Classic-mode-support-timeline/m-p/3640