Skip to content

Conversation

@kLabz
Copy link
Contributor

@kLabz kLabz commented Dec 5, 2025

No description provided.

@kLabz kLabz linked an issue Dec 5, 2025 that may be closed by this pull request
@Simn
Copy link
Member

Simn commented Dec 5, 2025

What problem are we solving here?

@kLabz
Copy link
Contributor Author

kLabz commented Dec 5, 2025

The linked issue, though a more general solution for the "does current haxe support X?" problem would be more convenient

@Simn
Copy link
Member

Simn commented Dec 5, 2025

wtf are linked issues... ok I see

I think we had this discussion before, but I generally don't want people to discriminate against preview versions and release candidates. That's one of the few things that distinguishes them from proper releases where we want to ensure a certain amount of backwards compatibility. We reserve the right to break anything between a preview version and a proper release, so users should be aware of that.

IMO the best solution is to just release preview.2 soon and tell everyone to update.

@kLabz kLabz closed this Dec 5, 2025
@kLabz
Copy link
Contributor Author

kLabz commented Dec 5, 2025

Makes sense; though I half expect them to just run haxe --version to grab the actual version instead, which is a bit silly 😅

@Simn
Copy link
Member

Simn commented Dec 5, 2025

Probably yeah, but we can just say that this voids their warranty!

@kLabz kLabz deleted the full-version-define branch December 5, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Haxe 5/Nightly] Versioning Issues

3 participants