Yes, this is accurate. If it helps bring peace to any current Blaze users, I’ll go on record and say this: MDG will continue to address critical bugs that arise with Blaze, that are caused by changes made to the Meteor core. I’m not really going out on a limb (or risking my job) by saying this, as this is what we’re doing now, and we don’t have any plans to change this. We don’t want to leave Blaze users in the dark (especially since Blaze is currently dependent on Meteor), and bugs caused by core changes are likely easiest addressed by those making the core changes. Please note though that this is for bugs caused by Meteor core changes, not long outstanding usage bugs or bugs that are introduced as new features / bug fixes are introduced into Blaze (which we’re leaning on the community to help out with).
Thanks for driving this Blaze discussion forward @arggh.