Yes, MDG will no longer maintain Blaze. In this sense post 1.4 it will be officially depreciated. The jury is still out as to what becomes of Blaze. At the moment things depends heavy on one man: @mitar.
I have yet to see much progress over on the repo ran by @mitar, which is really worrying as someone that has a production application running on Blaze tech. In fact, I'm now seriously looking at making the switch to React because of this situation.
Well put. I'm in the same boat as you. I created meteor-up-classic in order to get my deployment situation straight.
It's true, the tech that makes up meteor classic will all be depreciated at some point probably relatively soon -- Blaze, DDP, Tracker, Minimongo, Atmosphere -- all of it. The way I understand it, they will all become the community's responsibility (Atmosphere excluded) to maintain and grow -- or not. Hopefully each one of these will be put out on npm, but we can't be sure.
MDG's has a new strategy around, and focus on, Apollo. Post 1.4, from MDG's perspective, Meteor classic will become an integration point for Apollo.