TeamCity Release Cycle
Why Upgrade TeamCity
TeamCity is systematically and frequently updated with new features and optimizations. Each release introduces the following key improvements:
new functionality: including new runners, build features, UI enhancements, integration with third-party software, and instruments for customization.
New features are mostly released in major versions. To ensure smooth upgrade/downgrade between minor versions, bugfix updates do not add any important features but aim at fixing occurring problems.
performance improvements: one of the primary focuses of our team is to make TeamCity as fast and responsive as possible, which includes smooth UX, stable server performance, reasonable utilization of hardware resources, and many other aspects.
security updates: to comply with the industry-best security practices, we continuously analyze TeamCity and introduce multiple security improvements per release (for more details on security in TeamCity, read these notes).
bug fixes: thanks to our QA team and active user feedback, we can quickly catch and fix even rare bags. If we notice a critical bug soon after releasing another TeamCity version, it is our priority to release the respective patch or the next bugfix update as soon as possible, which makes it especially crucial that you don't skip regular updates.
Major updates are released twice a year, and each major release is followed by multiple minor (bugfix) releases.
A major release is represented with the
YYYY.N number, where
YYYY is the release year and
N is the serial number of the release during this year. For example,
2020.2 are two major versions released in year 2020.
A minor release is represented with the
YYYY.N.M number, where
YYYY.N corresponds to its preceding major release and
M is the serial number of the minor release. For example,
2020.2.2 is the second bugfix update released for major version