wxWidgets/docs/contributing/about-version-numbers.md
Vadim Zeitlin cf28473d9f Mention that wx.bkl doesn't need to be updated for micro releases
Only WX_VERSION_DEFAULT value, which doesn't include the micro version
component, needs to be updated in this file.
2018-12-10 19:06:18 +01:00

42 lines
1.6 KiB
Markdown

All about wxWidgets Version Numbers
===================================
## Where to update the version numbers
There are several places in the wxWidgets source tree that
define the version number for the library.
The script `misc/scripts/inc_release` can be used for incrementing the release
field of the version, i.e. changing 2.8.x to 2.8.x+1 but it does not take
care of version.bkl and can't be used for changing the other version
components, this needs to be done manually. It also doesn't update
version.bkl file which always needs to be updated manually, follow the
instructions there.
Here is the list of files that need to be updated:
build/bakefiles/version.bkl {C:R:A} [NOT UPDATED AUTOMATICALLY]
build/bakefiles/wxpresets/presets/wx.bkl [NOT UPDATED AUTOMATICALLY, not-micro]
configure.in
build/osx/wxvers.xcconfig
docs/changes.txt
docs/readme.txt (date needs manual editing) [NOT UPDATED AUTOMATICALLY]
docs/doxygen/Doxyfile (PROJECT_NUMBER and DOCSET_FEEDNAME)
docs/doxygen/mainpages/manual.h (just date) [NOT UPDATED AUTOMATICALLY]
include/wx/version.h
include/wx/osx/config_xcode.h
samples/docview/Info.plist
samples/minimal/Info_cocoa.plist
samples/minimal/borland_ide.cpp [not-micro]
Do not forget to rebake everything after updating version.bkl!
## When to update the version numbers
Version should be updated immediately after releasing the previous version
so that the sources in the repository always correspond to the next release
and not the past one.
See also [binary compatibility notes](binary-compatibility.md)