> ... we will very quickly have runtimes having Apache releases on their own cadence and the version numbers won't align with each other or with openwhisk core.
We have to fully realize this now --- otherwise, as I stated earlier, I don't see what we've gained from splitting the one repo into so many other than process overhead. If it makes it easier to cut the first release of all the runtimes starting at the same X, then OK from my side also. But we absolutely must recognize we will have to release different versions of the runtimes and a release of a new PHP runtime should not cause all the runtimes to be re-released. So to Rob's question: "Will all the other runtimes and OpenWhisk itself need to be released as 1.13.0 because the PHP 7.3 runtime was added to openwhisk-runtime-php?"... no releasing PHP 7.3 should not cause all the other runtimes to be released at a new version number. > I don’t understand how the versioning of runtimes will work so that users know that a given runtime works with a given rest-of-OpenWhisk. This is a good question we haven't addressed. I would expect that when we cut a release of a future version of openwhisk, it should specify the version of the runtimes that it is compatible with in the runtime manifest. We did not do that for 0.9 nor could we, since the phase ordering was backward. -r
