在 2026-1-13 19:00, Luca Bacci 写道:
Hello,Users often rely on the __MINGW64_VERSION_MAJOR macro either for feature detection or to work around older issues. However we increment __MINGW64_VERSION_MAJOR right after a release. For example, mingw-w64 13.0.0 was released on 2025-06-08, and the macro was bumped soon after branching (on 2025-06-05): https://github.com/mingw-w64/mingw-w64/commit/b45abfe When code checks for __MINGW64_VERSION_MAJOR >= 13, the developer expects mingw-w64 13.0.0 as a base. Instead mingw-w64 could be a development snapshot made a after the 12.0.0 release. Note that MSYS2 uses development snapshots. Most Linux distributions use offical releases only, but users could package mingw-w64 themselves (e.g. AUR).
Personally I use this scheme:
BRANCHES | master releases/1.0 releases/2.0
---------+-----------------------------------------------------------
TAGS | ...
| |
| v
| 1.0.alpha
| |
| +-------------\
| | \
| v v
| 2.0.alpha 1.0.beta
| | |
| | v
| | 1.0.rc
| | |
| | v
| | 1.0.ga (major)
| | |
| | v
| | 1.1.ga (minor)
| | |
| | v
| | 1.2.ga (minor)
| | |
| | v
| | ...
| |
| +---------------------------------\
| | \
| v v
| 3.0.alpha 2.0.beta
| | |
| | v
| | 2.0.rc
| | |
| | v
| | 2.0.ga (major)
| | |
| | v
| | 2.1.ga (minor)
| | |
| | v
| | 2.2.ga (minor)
| | |
| v v
| ... ...
--
Best regards,
LIU Hao
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
