Consider using SemVer for versioning about luau HOT 3 CLOSED

FWIW right now our plan is to follow Roblox version releases, as this is where the majority of the changes are going to come from. It's essentially major.minor where major is always zero.

from luau.

SemVer, if implemented, would most likely be for header file / ABI compatibility, not for Luau source code compatibility. I don't think Luau needs SemVer, personally. I think the current strategy of following Roblox releases is the best one, especially since it doesn't discourage contributors from making breaking changes to the API for soundness reasons or refactoring (method signatures and etc.)

Right now the main usage of Luau is in Roblox, maybe once luau-rs is out it'll become more accessible to other applications, but the goal is that even if Luau changes out from underneath, those changes won't bubble up to the public API unless they're pretty darn big. luau-sys contains all the unsafe, raw bindings, and luau consumes them and smooths over them with a consistent & safe Rust layer.

I don't see breaking changes hurting my library too much, as I can simply update; I don't imagine the situation is too different for most others either, though maybe they have some thoughts on this too. It might take a bit for them to show up again after interactions became re-enabled on the repository.

from luau.

I think the conclusion here is that for now, semver as in "non-0 major version" is too early for us to decide on and switch to. When the language matures we could choose to bump the major version, but we'd need to decide what exact compatibility guarantees that provides (including embedding APIs etc.). We're unlikely to get there in the next year or so so I'm going to close this for now.

from luau.