This is intentional and is the way that QEMU release candidates are versioned.
The versioning scheme is MAJOR.MINOR.PATCH where: 0 >= PATCH < 90 is a stable release PATCH = 90 is the development window for the next MINOR release 91 >= PATCH <= 99 is a release candidate for the next MINOR release This means 2.7.93 is release candidate 3 for 2.8. I suppose one reason this scheme has been used is that simple MAJOR.MINOR.PATCH version comparison algorithms will work correctly even if they do not support -rcN notation. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1650175 Title: wrong version in 2.8.0-rc03 Status in QEMU: Invalid Bug description: When you compile qemu the version still 2.7.93 instead 2.8.0-rc03 build/config-host.mak:VERSION=2.7.93 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1650175/+subscriptions
