Firstly big thanks to the guys that have been working on this - really appreciate your efforts.
A clarification question if I may: is my understanding correct that the latest version (1.1.2.1) has a known bug in that if you close your synch'd wallet the local blockchain copy will be "lost" and you will need to re-synchronise?
Assuming that is correct then we are waiting for a further update to the client?
Would it be sensible to update the OP and the website with:
a) info about the known bug and how to deal with it so people are aware;
b) an estimate of when the next version will be released; and
c) some guidance as to whether people should update now (and live with the bug) or wait?
I would advise you to wait. There are more bugs than just that and they could potentialy destroy this coin if it gets out of hand... this is why I have neglected putting up the wallets (or really doing anything). You should be fine updating to 1.1.2.1 but keep in mind tomorrow there will be yet another MANDITORY update. Yes im sorry if this feels like we are using you as Beta testers for our updates but with the amount of hostility going on in this thread it has caused us to want to get our updates fixed as fast as possible. The reason this last one was released so quickly was because of the large amount of forks going on and we didn't want to completely lose the coin. Though in our hast we only created more problems while fixing others. So please have some patience. We are doing the best we can while working with a new coin concept.
That being said... STOP SOLO MINING! at least until we can get the network stable. Mine in Anomalypool.com for it's nodes are hardcoded so it will never fork! You can still mine in anomalypool without a working wallet. As long as you had made a wallet prior to all this crap and you don't delete your wallet.dat you will receive your coins!
I hope you don't take what I've said as hostile. If so, you're taking it exactly backwards. I (for one) don't want updates as fast as possible. I want them as good as possible. I've said all along
not to rush, and
test thoroughly before you release. C'mon dude, you're not using us as beta testers, you're using us as pre-alpha testers. In a real company, that last release would get someone fired.
Here's what I said before:
When GIT is updated with the hard coded nodes and the patch posted earlier and s4w3d0ff gives me the OK, I will go ahead and compile the latest version.
Are you going to test it before you release it? I know there's a rush to get out a good wallet, but at this point, if you release something broken, things could get brutal.
Well. Surprise.
You can't flip the bird at, Murphy's Law, Common Sense and software engineering 101 without repercussions.
All this may sound harsh, but if you were delaying things to fix bugs or test a newly compiled client, I'd be the first to defend you.
The problem is that the forks needed to be fixed asap, this had top prio to ensure nobody mines on a wrong chain and loses earnings. The devs do what they can - and yes, I see your point about code quality and tests
I understand that, and I understand this is all hard work. But you still have to test things. Period. Rather than putting out that client, you could have simply told everyone not to solo, get on anomaly and don't worry because the coins are in the mail. It's infuriating because this coin has promise, and I respect you guys, but c'mon, you
know you know better than to go from compiler to download link in one fell swoop. All this rushing is just making your job all the harder.
Again. Take all this as tough love.
And on the bright side, nobody's bitching about getting it on an exchange anymore.