I guess. It just seems like at some point you fix the issue and pull the trigger. I bet they could really test the hell out of it in 3-6 months, but that would obviously not be tenable.
My concern is that they are pushing back the really important stuff, like RC4, to test such a "straightforward" solution. Sometimes an excess of caution can be bad.
Well, Evan's modus operandi is to set a date of release as soon as he feels it's ready. So it may not take 3 weeks, but he's giving himself as much space as he feels he needs so he doesn't have to postpone more than necessary. He already sees the solution to today's problems, so it's just a matter of coding it.
Also, what has Evan been doing since he set today's fork date? Do you think he's been sitting back partying? I doubt it, he's admitted he loves to code with his headphones on, in his own world. I am certain that a LOT of what RC4 will contain (top secret, LOL) is well started

Not a bad day. We really needed to do this, because we don't have the hashing power on testnet, and the numbers in general for this kind of thing to have popped up. Actually, I kind of thing of today as being quite successful in the progress of the coin.
BTW Camosoul, if you're really buying everyone's coins, I want to marry you! Heck, I'll even vet all your hookers, make sure they're top quality! I'll run your household, but I want half of your worth, LOL. Only problem is.... I'm already married...hummmm, LOL
Good points. In that case testing RC4 is the bottleneck, and my argument still holds (delays to RC3 delay the release of RC4 since it will require time to test, even if it is completely coded).
Anyway, I do trust Evan and the team and I'm certainly content to let them do their work. I do hope that they move the date up so we can put RC3 to bed and move on, but I'm sure they will do what they feel is best.