You're correct, we didn't change the version name "1.0 RC1" to "1.0". Our fault. We're aware of that.
We just talked and decided not to auto-update to alpha/beta/... version, we also find useful to include an option to let the users be able to auto-update to that versions (in short : alphas, we also could refer to them as "non-stable").
That functionality will be include for sure on 1.1, but we don't know when yet (as soon as we have free-time, as it's not our max priority right now).
Our roadmap is something like alpha, beta, gamma, delta, release candidate (also know as RC), and the " official release".
After one week of hard work, we packed everything and release it under a greek letter name or the RC. They should be stable, but they're not tested as much as we want. For those who have specific problems.
Once the RC is out there, we spend another week to test it and fix every single error we find. No new functuonalities are added on this week, not big changes, keep it stable. Our "final" product, for everyone.
We want to deliver high-quality software but also a very useful and flexible tool, so only the "official release" (which is tested) will be on the auto-update for the moment. The other releases should be "unzip and copy over" the old installation (hey! do a backup before), in some cases additional instructions will be required.
So... in short: Yes! it's because it's nor the official release yet.
