I think we should just release as @latest for all @babylonjs/*
Otherwise people will get the old alpha.
then when we release 4.0.0 we can start tagging the new releases as @next since that seems to be what most frameworks do.
We could setup a CI to automatically do a @dev release also, that could mirror the master branch.
@latest = latest semver release
@next = 4.1.0-beta
@dev = 4.1.0-dev.master-dc36dbc (where the last bit is the sha1 git hash)
That way we can always force install a specific version to test if a bug is present.
But also for some of us that are on the bleeding edge, can install the latest build.
Some might say that you should install the @dev builds directly from github, but since that doesn’t contain our builds, thats a no go.
I recently helped angular @ngxs to do something like this using circle ci.
So if you need any help with setting up a CI server I could be of assistance.