Publicly expressing my concern about the hard-coded hard fork to 2.0

[liondani]

that's why it is unwise to update to 0.9.3 prior we test bts2.0 with devshares!

Then why was the upgrade released and then announced?

https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.3
https://bitcointalk.org/index.php?topic=1182483.0

Also, people are actively being encouraged to upgrade on this forum:

https://bitsharestalk.org/index.php/topic,18477.0.html

that means that they are confident that everything will go just fine and that's a very  good sign...
but that doesn't mean that all delegates must blindly follow the "orders" before evaluating them-self the situation and actually testing the bts2.0 chain...
Because in that case it's like we have a "one-point failure" possibility. We should eliminate even that tiny possibility...
It's not wise we upgrade all simultaneously ... we can do it slowly as we reach .... 13 of October 2015 (potentially a historically day!) 

[monsterer]

that's why it is unwise to update to 0.9.3 prior we test bts2.0 with devshares!

Then why was the upgrade released and then announced?

https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.3
https://bitcointalk.org/index.php?topic=1182483.0

Also, people are actively being encouraged to upgrade on this forum:

https://bitsharestalk.org/index.php/topic,18477.0.html

[liondani]

that's why it is unwise to update to 0.9.3 prior we test bts2.0 with devshares!
I personally suggest we upgrade near the snapshot date... (normaly couple of days before snapshot everything will be smooth so nobody will make a second thought's about upgrading)...
The worst case scenario would be to delay the hard fork without needing to downgrade our clients to 0.9.2 again!!!!

PS I will be more confident after the "official" devshares2.0 test net.... so i wait a bit for the upgrade.

[cass]

i'm intend to agree on testnet run for min. 1 month before fork!
But to be honest, i'm currently not that into .. how difficult these problems on wallet currently are!

[escalicha]

Very good post. Fix a date of work with testnet with bug its little dangerous... 

[wuyanren]

No windows？

[monsterer]

Now that the 0.9.3 scuppering upgrade has been released (https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.3), the hard-fork is set in stone, which means, ready or not, the chain will expire on the October 13th.

The testnet for 2.0 isn't working yet (https://bitsharestalk.org/index.php/topic,17962.msg236734.html#msg236734). This is a huge concern. These things are extremely complicated, and done wrong, or rushed out the door, this could completely undermine confidence in the platform.

In my opinion, the testnet should have been running fully functional,  and without bugs, for 1 month at least before scheduling any kind of hard fork.