Absolutely. It is too soon to focus on the price. Everyone who's in so early should be ready for some bumps in the road.
I think fernando got it exactly right. I know everyone is frustrated with this last glitch. I'm sure none more than the developers and testers. However, it is important to keep in mind that this is still beta software; not even v1.0 yet. Delivering flawed/buggy technology faster benefits no one but competing coins and day traders looking for more ups and downs. It isn't good for the long-term viability of Darkcoin, so I'm happy to let them hammer on this thing as long as it takes to get it right.
A major reason that they missed this timing problem was that their test group was small enough that it was unlikely to generate such a rare condition. Now they are investing time in creating a more robust testnet which will pay dividends in future testing and debugging. I'm glad to hear it.
, we have bamboo and a ci.something.com, we also have di.something and stage.something, then production.
I disagree. Like AlexGR, I believe development should be as transparent as possible and I support him posting the IRC chats on bitcointalk. It's not as if they were PMs or private conversations; #darkcoin-test is open to the public and I think it should stay that way. Of course it could be taken out of context, but so can posts from anywhere else. So many coins try to sugarcoat or hide negative aspects of their development from their users/investors. I don't want Darkcoin to become like that.
Flare: this is awesome. I thought I was at work for a minute
If someone has documented the qa use cases, maybe we could have a tasklist on the wiki, or bugzilla or something, then the testers could take a use case(or be given) and test it and report on it.
I am looking forward to seeing how the votes will be changing the hash of the block. Will the block header be changed to include a hash of the master node votes in the same way the merkle root is a hash of the transactions? As the developer of the android wallet, I hope that the changes don't break the SPV requirements that are part of the android app.
Make sure you email Evan! He's building a team and you sound like you'd fit in beautifully!
Yes but it would be good to organise it a little more and for AlexGR to become "official" in some sense (Perhaps he already is and I don't know this :grin
Keep an eye on the testing subforum. We will start testing the new block hashs on testnet next week. New source code (testing branches) and binaries are incoming.
i totally hear you
I think your comparison is not valid. We are talking about open source here! Your will get competitors being on par in functionality if darksend is released. Only way to be ahead of the race ist to be the first and stay there by innovation. In the meantime, you should be as transparent as possible not trying to hide your intentions.
Sure transparency is good and needed
In general you are right, but a vital part of crypto projects is the community. Your success is based on the community supporting it and you should not lock them out. All coins have still a long way to go mainstream and being widely accepted financial assets. I think and hope we will reach this stage sometimes - I'm on your side then.
Sure. I would be more than happy to look at them. Are you planning automated testing as part of continuous via Jenkins or something similar?
Will do!
Exact, i have already set up a CI server at http://bamboo.darkcoin.qa - i still need to tweak the Buildsystem/makefile a bit, as it does not support cross compiling yet, but once i have that up and running i want to continue setting up the automated tests and gather some metrics (code coverage, cyclic complexity, ...)