Actually you have that backwards ...

v1.3.5 has several bugs where v1.3.6 is pretty stable based on all the reports we are receiving ...

Sounds like you have experienced a bad upgrade vs a bad release ...

You might try the upgrade in a test directory with a test database and see if the next go 'round doesn't work better for you ...