How to bucket OpenD to releases?

[dukc]

Hello, I'd like to try my hand at building OpenD with Nix and possibly supporting it at dlang.nix.

There's one problem though. The raison d'atre with Dlang.Nix is that you can pick what version of the compiler you want - you don't have to use the most recent compiler we happen to support, so your code will keep compiling. There doesn't currently be a versioning scheme for OpenD though, so it seems I will have to come up with my own.

Do you have any opinion on what would be a good way to pick "releases" to support from the GitHub history?

Ping @adamdruppe @GrimMaple @PetarKirov

[adamdruppe]

OpenD has exactly one supported release: the current one. There will be no official way to download an unsupported release.

You're free to download it and keep a copy somewhere though.

[dukc]

I'm not expecting support for older releases, any more than I expect support for old DMD releases. I'm just looking for a good way to pick what versions to build (and offer to others if i get that far and @PetarKirov doesn't protest). With upstream the choice is obvious: the latest patch release of each minor version.

I can of course come up with my own scheme, but I'm wondering if you have any preference on what versions I'll pick.

[adamdruppe]

Also note that opend's bar for breaking changes is generally higher than upstream; we don't break code without good reason anyway.

[crazymonkyyy]

maybe just have a yearly release "openD2025" for the auto updating tools