Every project has such "uncertainty and FUD" phase in it`s development, it`s a common practice. No surprises.
Main thing is that team delivers upon time, as mentioned in roadmap.
Agreed. However not every team handles it in the way the nix team is doing. That's what bothering a lot of us.
It also isn't only fud. Just reporting bugs, or asking when feature / bug x will be fixed is enough to get banned.
But yeah, let's move on.
2.0.3 is out, and too bad has some really basic issues which should not have been there if it was tested. Small issues, but annoying issues that do not help getting this 'polished' feeling you would expect from a professional team.
1) Ubuntu LTS versions (16.04, 18.04) not supported by the released binary. Workaround: compile manually.
2) Mac installation gives an error when trying to upgrade from 2.0.2. Workaround: delete the 2.0.2 app before installing 2.0.3
3) There is still an open issue (#16) on GitHub which provides a fix for the daemon randomly crashing when executing RPC calls. This has not been patched yet in 2.0.3.
4) Block height counter jumps back to 0 while syncing.
Show Posts
please change it
