Still planning a release on the 13th? How long has the most recent testnet lasted?
Although BM has expressed his strong confidence for a 10/13 hard fork release, I too share some of your reservations monsterer. There are a myriad of details yet to be completed. The time is getting very short and I for one would like to see a test strategy for the testnet and advanced notice of what the goals are for all tests to be done before launch.
"spamming" tests that clayop is doing have revealed some weaknesses and your point about how long lasting a given test is able to be sustained before the test must be restarted or a new checkpoint established is not very long.
If these transaction flooding tests are killing the network at only 10% of our published throughput claims that won't play well for us in the marketplace. It could only serve to weaken our already weak standing in the crypto world.
Clayop has published a poll asking what TPS goal should the next testnet strive for, but I'm not sure throughput and high performance should be the focus right now. On the other hand perhaps that is exactly the best approach to uncover bugs that threaten the reliability and robustness of the network.
I would like to see a set of several VPSs setup as seed nodes and witnesses configured with failover tested. I haven't explicitly looked for it but I would love to see docs or forum threads talking about how to best implement failover for graphene witnesses. Wackou and I have some ideas, not only for DDoS protection and small world backbone + seed configuration, but also how to monitor failures and what to do when they are detected.
BM indicated in last Friday's mumble there isn't time to address the code changes wackou has proposed before the 13th, but we need to get busy and get a testnet in place that is robust enough to be a live production setup if it had to be.
Xeroc is busy working on documentation, and has written a migration document that described quite well how to export a json file from 0.9.3 for the purpose of importing account balances into graphene. I was under the impression users would not be required to perform an export / import operation, all accounts and their balances will be migrated automatically so long as they are in a fully synced wallet with no outstanding transactions pending. Perhaps I've misunderstood the purpose of those docs, maybe they are not intended for the general public.
It may not be possible or considered important enough but I would very much like to see cli wallet commands documented individually like they were in the 0.9.2 client rather than the entire list splatted to the screen. I can appreciate that hasn't been a priority, and not be very important to do before release, but I really miss the way it used to be in 0.9.x.