@holiman :thumbsup: :thumbsup: :thumbsup: That's great! @winsvega is doing a great job on the execution side, to complete the picture it would be great if you could also extend on communication with the new hire, atm it is hard to get e.g. the latest state of the Constantinople implementation or generally a picture what is happening related to tests.
Stuff I would value a lot here:
Just some wishlist. :smile:
CREATE2
. it should be ready by tomorrow. But it turns that we won't be ready to publish a release before Ropsten fork block happens, so, it'll be available only in a Snapshot version. But it doesn't look like a big problem and we're ok on keeping 4_200_000
for Ropsten
Tweet served its purpose :) . I am here saying we heavily use ropsten for testing our contracts atm. We are rather close to mainnet release and really don't want to add the task of finding another testnet on top of my team right now.
How bad would it be for you if there was a chain split?
Would effectively make testing almost impossible. Say a chainsplit between parity/geth. Half of us use parity, other half geth to test both clients.
How long would you manage without a non-broken ropsten?
I don't understand the question. You mean for how much longer do we need a testnet?