This is how release numbers work it most wont be 1.0 until its well tested and out of beta. Works this way with all programs
To clarify: not being 1.0 till it's out of beta is that way for all programs. Some programs, however, do follow decimal versioning notions where there is no version 0.10 -- next after 0.9 would be 0.92 or something. Linux, as one example, was this way for a while, and then had an odd/even development/stable scheme for a while, and now has development and "stable" releases in the same minor (2.6).
Lesson: Never assume anything about versioning systems.
After installing Fanoush's 48 MHz kernel, I installed Mer on my NOkia 770 using instructions on Mer wiki. Everything seemed to work, I entered user name password tablet name , but then nothing came up. Only thing I see is the background image. I waited for half an hour and restarted. Still nothing except the background image. Is there a way to see booting up messages, see what's wrong
This is how release numbers work it most wont be 1.0 until its well tested and out of beta. Works this way with all programs
Hmm. In that case the mathematician in me would have preferred to see leading zeros. Going from 0.01, 0.02, ..., 0.09 to 0.10 would then be fine! 0.9 sounds very much likely it was nearly ready for release.
in case someone could be interested i got wireless ad-hoc working properly by disabling network-manager and setting up things with iwconfig, ifconfig, route and editing /etc/resolv.conf.
Hmm. In that case the mathematician in me would have preferred to see leading zeros. Going from 0.01, 0.02, ..., 0.09 to 0.10 would then be fine! 0.9 sounds very much likely it was nearly ready for release.
It's to be understood as major.minor and i think we'll jump to .97-98-99 when we approach 1.0
i found the problem with the mer installer and the bootmenu.
the installer writes wrong item file on advanced install. So i started an installation with simple mode, after writing the boot item i interupted, and installed without writing bootmenu item. I edited the item (it was saying simple) and run refresh-bootmenu.d. Now it's OK.
v0.10 image failed to work properly so we're skipping this sprint release, v0.11 release afterwards a 2 week development + 1 week testing. (Hildon input method problem, artwork problems, etc).
v0.10 image failed to work properly so we're skipping this sprint release, v0.11 release afterwards a 2 week development + 1 week testing. (Hildon input method problem, artwork problems, etc).
