Make no release before it is ready. 
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
Testing has shown that it is not yet ready for general release. It will be a couple more days before 1.3.0 comes out.
darval where did you get this information?
As I mention in a the quote you used, the sia slack, the contributors channel in particular which is where taek posts the upcoming release candidates.
http://siatalk.slack.com
There is currently a RC6 candidate there. Because of the scope of 1.3.0 changes, they have found quite a bit of problems and are unwilling to release it until they get them all resolved. RC6 resolves the problems they have seen to date except one (that I am aware of). Because of the instability tho, I wouldn't update to them unless you are willing to deal with some of these issues and provide feedback. If you are, please do join us and help test the upcoming release.
When I was doing it the client automatically starting updating itself to v1.3.0
Everything went fine and it keep all the blocks I received previously before shutting down the client.
So all is good with the update and will let you know when it has fully synced.
Now I see why you would need a ssd to do this because I am on day eight now(on and off and not straight!
). 