yes, lets vilify everyone who has had their uno shanghai'd by terrible dev conduct.
at you 32bit guys, i wish i could assist - i really do.
IME, its the squeaky wheels that get the grease.
go right to the source, make your feelings heard but remain mature & polite.
this among other things should NOT have been overlooked!!
It wasn't possible to predict both devs would be unresponsive/indisposed at the same time. Very inconvenient. I hope I don't spill any secrets when i say that FK actually did prepare a contingency plan, but that fell through too, so there really was a lot of bad luck involved! Anyway, he has been busting his ass making things right and has already achieved much. Please don't forget we're all volunteers, doing this on our own time. This is not meant as an excuse, errors were made, but that is human.
As you can see by the addition of CaptChadd we're already actively recruiting additional devs for UNO, so that the work can get better distributed and we don't get into situations again where we rely on the availability of a single person. This is only the beginning, and everybody is invited to do his or her part in making the future UNO even better than the past...
As for the 32bit people, it won't be long, I'm fairly sure of that!
Slightly OT:
I actually tried setting up a Windows dev environment to compile the wallets - it was worth an attempt but I failed. Tracking down all the dependencies in their required versions is already hard, when the error messages just wouldn't go away and google couldn't help I gave up. Really made me appreciate the great tools for dependency management, deployment etc. that I've got for my webdev jobs, so much more comfortable. I'll keep looking for a good guide to try again.
