Quote from: 7000years on June 21, 2014, 12:54:21 AM

Quote from: AlexGR on June 20, 2014, 11:55:05 PM

Quote from: 7000years on June 20, 2014, 11:33:37 PM

Quote from: Denada129 on June 20, 2014, 11:15:47 PM

Its going to take one more month for what you call "simple problem" ?

It'd be better to let the devs work without the stress of the market so that they deliver a bug-free feature. IMO the coin's reputation cannot afford a 3rd failure to migrate to the new payments system. A quick & dirty fix that could possibly lead to another problem is by far worse than waiting for some weeks. My 2 cents

When the first delay occurred, people were like "if there is a second delay, the coin will die".
When the first fork happened, people were like "if there is a second fork, the coin will die".

It seems to me like the benchmark is always re-positioned to the next possible make-it/break-it point to add extra excitement and drama.

If people have unrealistic expectations of what a development project is, that's their problem. I think the market is showing tremendous levels of maturity and now understands the situation far better.

I'm not saying a 3rd failure would be the end, but it would definitely have an impact on the coin's reputation.

The bottom line is that the migration plan was not good.

Migrations happen everyday on very large scale systems. Nothing breaks, because there are good and well-tested migration plans.

Please, keep in mind that there is a serious amount of money that is being traded out there. Be professionals and have a good migration plan next time.

Please keep in mind that never has a migration like this been done. In the history of computers. So realize that these successfull migrations you are talking about stand on the shoulders of countless failures before them to learn better methods.

The plan was quite solid. The problem, was a race condition was introduced, that it is unlikely 6 months of testing, without production level hashing power, could have determined. It was much better to be discovered now, then to have caused larger issues later, when no one would have been watching for it.