Conversation
* Split the version definitions into a version_defs.h * Version.rc uses version_defs.h, with the help of some extra macros * The NSIS installer script parses the values from that header file * Split off the build type revision number (for ALPHA, BETA, and RC) into a separate definintion. * Use STABLE for all stable branch releases instead of just the first release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This simplifies the release process by moving the version definitions to a separate header file and then referencing this from other files. This header is directly used by the Windows resource file and the NSIS installer script, and used by a new python script that updates the version number in the README, configure.ac and the Xcode project files.
This splits the numeric part of BZ_BUILD_TYPE (for ALPHA, BETA, AND RC builds) into a separate BZ_BUILD_TYPE_REVISION definition. into This also changes our process a bit and uses "STABLE" for all releases from a stable branch instead of just using "STABLE" for the .0 release and "MAINT" for all subsequent releases.