1175461030
The new versioning system is based on the versioning system used by the GNOME Foundation for the GNOME desktop. We are dropping the "major version" as defined by SemVer and move to a version number with a most and least significant number. The most significant number must be incremented, if there are new features or significant changes since last major release. Otherwise, the least significant number must be incremented, if there are only minor changes since the last release. New features or significant changes mustn't be introduced by a bump of the least significant number. If a minor change would introduce small user-facing changes (like a message-box or slight UI changes), it could still be classified as a minor change. At the end of the day, a human shall decide, if a change is minor or significant, as there is no clear line that would separate a "minor" and a "significant" change in a GUI-application. Definitions: feature: New user-facing functionality significant change: Something that changes user-facing behavior minor change: Something that fixes unexpected behavior Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
30 lines
906 B
Plaintext
30 lines
906 B
Plaintext
#ifndef WIN32_LEAN_AND_MEAN
|
|
#define WIN32_LEAN_AND_MEAN
|
|
#endif
|
|
#include <windows.h>
|
|
|
|
IDI_ICON1 ICON DISCARDABLE "polymc.ico"
|
|
1 RT_MANIFEST "polymc.manifest"
|
|
|
|
VS_VERSION_INFO VERSIONINFO
|
|
FILEVERSION @Launcher_VERSION_NAME4_COMMA@
|
|
FILEOS VOS_NT_WINDOWS32
|
|
FILETYPE VFT_APP
|
|
BEGIN
|
|
BLOCK "StringFileInfo"
|
|
BEGIN
|
|
BLOCK "000004b0"
|
|
BEGIN
|
|
VALUE "CompanyName", "MultiMC & PolyMC Contributors"
|
|
VALUE "FileDescription", "PolyMC"
|
|
VALUE "FileVersion", "@Launcher_VERSION_NAME4@"
|
|
VALUE "ProductName", "PolyMC"
|
|
VALUE "ProductVersion", "@Launcher_VERSION_NAME4@"
|
|
END
|
|
END
|
|
BLOCK "VarFileInfo"
|
|
BEGIN
|
|
VALUE "Translation", 0x0000, 0x04b0 // Unicode
|
|
END
|
|
END
|