I would like to remind everyone that the fact that teams like Raiden and their users are testing on the public test net is actually good for that public testnet. It is much more likely to get bugs discovered than a testnet without any users (because it was broken for few days and everyone had to migrate to another). I would still recommend to complete pre-testnet testing before pushing for the test net.
I would even say that it makes sense to create a new PoW chain just for core devs for a little while, and once it has gone for a few days without issues, do Ropsten fork
We have to respect the users of Ropsten, because they help us test the new release
I am a side-chain developer but I still use ropsten to test my contract
Let them use Ropsten "Classic" chain :joy:
@holiman you made the tweet asking for projects to tell you if they use Ropsten. I just did. We would have more work on our plate if Ropsten breaks this month and this is a critical month for us.
It's obvious that our priorities are very different and in the end it's not my decision. From the way my comments here were received it sounds like a done deal, so we will try to plan accordingly.
I suggest to launch a temporary testnet just for core devs (like a DEV environment) to just see if there any obvious problems and do a bit of poking there. If that works, move it to Ropsten (UAT environment :) ). That obviously requires delaying Ropsten, and I actually thinks it sends a positive signal rather than negative (if this is a worry). And, if the worry is to start testing as soon as possible - by keeping Ropsten stable, rather than shaking all the users off, the quality of testing will be better, even though it will start later
We're about to make a release
So as long as people are still mining, I don't think it will actually matter a lot to @LefterisJP's workflow -- there may be higher blocktime variance, and his/her transactions may get confirmed on another chain, but that's all.
Continuing to run the pre-fork Ropsten is also an option.
I don't care either way, as long as Geth and Parity agrees on the same thing
@5chdn @folsen call it please
or do we want to call it off altogether for now?
and aleph, of course
Or an alternative 4,567,890
4230000 is 10 days from now, which is 14th of October
Sunday
we really don't want to consensus fix the week before devcon
we really don't want to consensus fix the week before devcon
I wholeheartedly agree with this
Will the hive with the new versions be able to be running by then?
Hive always runs on latest code, and latest master on tests.
See https://gitter.im/ethereum/tests for info about testing in particular. Afaik, there are a lot of changes not yet merged to master