FWIW, In Erlang Land, the "A" release (eg: 16A) is the "beta" and the "B" release is the "finished" release.
So 16B is the complete, ready for production version of 16.
Next release will be 17A, or 16B2 if there are bug patches required.
Also, it may seem weird that a "programming language" is having an update each year. (how many times a decade is C++ updated?) But this is because erlang is really a complete platform. The language is just part of it, but OTP, the platform is a hidden gem that gives erlangers super powers.
This also means, each year, your code gets better as the platform itself gets better.
So 16B is the complete, ready for production version of 16.
Next release will be 17A, or 16B2 if there are bug patches required.
Also, it may seem weird that a "programming language" is having an update each year. (how many times a decade is C++ updated?) But this is because erlang is really a complete platform. The language is just part of it, but OTP, the platform is a hidden gem that gives erlangers super powers.
This also means, each year, your code gets better as the platform itself gets better.