Yes, that is correct.
By the way, I noticed that we need to run the upgrade command twice as it will throw up the error mentioned by @theRKF above when you run it for the first time.
@Pong @NiteWave You guys aware of this bug? We noticed it when we upgrade to 5.0 on a few test servers.