Gavin Andresen,

Horrible work.  Absolutely NOT impressed.

You have >100 bugs open and yet decide to release on 30-march and FORCE the update for 1-april.  Just two days later.

This release is unstable as hell.  I get crashes.  I get unexpected exits.  And I get failures to restart.


Crashes:
-----------

************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::txn_checkpoint: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in ThreadMessageHandler()


Unexpected exits:
--------------------

04/05/12 11:38:48 sending: inv (73 bytes)
04/05/12 11:38:49 received: addr (31 bytes)
connection timeout
04/05/12 11:38:49 received: addr (31 bytes)
trying connection 200.74.242.32:8333 lastseen=-2.3hrs
04/05/12 11:38:50 received: addr (31 bytes)
04/05/12 11:38

--> Result code: 139


Failures to restart:
--------------------

Loading addresses...
dbenv.open strLogDir=/home/XXX/.bitcoin/database strErrorFile=/home/XXX/.bitcoin/db.log


************************
EXCEPTION: NSt8ios_base7failureE      
CDataStream::read() : end of data      
bitcoin in AppInit()      

--> Result code: 134


What about good Q&A procedures?  What about testing stuff before release ("compiles fine on Win7" is NOT testing)?  What about establishing a stable status quo BEFORE forcing it on people, like for a month/year?


I get 80% orphans with the old version, and I get 95% downtime with the new version.  Great choices, thanks a lot for that.