Then CryptoVote will have to compile again and if the majority isn't updating then pushing the update is worthless
I don't mind re-compiling for Windows. If we give users at least 2 months to upgrade, we might get the majority of clients. This also gives us adequately time to test and work on the next version. Microsoft and others have pushed some bad patches in the past so some folks wait until the the new version is well tested before considering an update (you know once bitten...). Others don't care or don't know about it.
Let's do that then, I will modify the code to Fork in November 5 (Remember, Remember the Fifth of November)
What about forking issue? Shouldn't new qt stay within current block until November 5th? Problem with previous RC3 was it forked before the reaching the 18800 whatever block height it supposed to forked at, creating a rogue block. To me that core of the problem. Am I wrong?