Main risks are passed now; that either something subtle in the update caused widespread issues, or that we couldn't get enough updates before the fork occurs. With 44% of the active clients updated, and that number increasing daily, we should be around 60% at least by the time the fork occurs, which is certainly enough for it to stick. An alert message has gone out over the network to ensure people are aware they need to update, too, and we'll have articles on post-fork updating for everyone who misses the deadline.