Please, it was not an update problem. I'm not a lazy pool operator.
I updated before and even tested on testnet. You can find my posts on darkcointalk for testing compatibility with NOMP. Chaeplin replied and I replied that it works well too. You can find my comments even on github.
You know what happened at previous release. I was monitoring if fork happens again.
Yes, this is my most concern about this update.
Orphan blocks are determined quite quickly at normal case, but it didn't appear that quick as previous.
I think it jumped block chain but auto synced a bit later which is added from this release.
I have seen many other coin blocks determined as orphan since I'm running many coin pools, and it didn't take long time like this.
I was suspicious about the phenomenon and I asked about it with this.
"fork occurred?"
Did I act like a troll or told everybody to dump? No. Sorry that it seemed like that.
It was just a mistake and I was so sensitive about it. I even opened new tab to write PM to evan.
Sorry about my mistake again.
Thanks miningpoolhub, appreciate your input.
Unlike others here that only want to hear positive news, I want to hear the real news.