Only if rc4 works, i hope that. but rc2 fail ad rc3 fail two times. RC4 please make me happy

RC3 was reverted once not twice -- it is now working with 99% pool compliance. RC4 is also a "spork" -- i.e. even if enforcement causes problems it can be turned off seamlessly. I really don't think there is much to worry about in terms of RC4 "not working".
I don't think RC4 will use enforcement(spork).
RC4 would be timed-fork(enforcement on), and spork would be used for failsafe.
Is that a guess or has that been confirmed somewhere? Could have sworn I saw eltito say the opposite.
Just a guess.

LOL
Well El presidente's guesses are better than most. I just wonder if there is enough time to test and give enough lead time for a hardfork by the end of July. A spork could be just 72 hrs or so of lead time, but a hardfork is at least a week. And as far as I know testnet validation is yet to get underway...
A hardfork is at least a week... ? What do you mean by that?
A fork is instant, and network consensus should be extremely quick given block time of (2.5 mins * 6 confirms) / block solving variance
I don't think pools will be at all happy with a "hit-n-run" hardfork. It needs to be announced well in advance to give people the time to update their daemons less we have half the pools/exchanges on the wrong fork and mighty angry.
(Btw, I am not talking about a spork where the switch is flipped after most have upgraded -- rather about a traditional hardfork, which is the same as releasing RC4 with enforcement enabled.)
It has been announced for quite a long time! And with spork already set right now, that is a non issue. Since 99% of pool have upgraded, 99% of pools will feel no difference when the fork is set.