News

Over the past few years, TeamCity has been using the YYYY.R versioning scheme, where YYYY represented the year and R represented the release within that year. When looking at the version number 2021.2.1, for example, you could easily understand its meaning: Similarly, the name of version 2022.1 EAP made it clear that this was an early preview of the first release for 2022. Why do we need a new versioning scheme? While this versioning scheme worked great for many years, the release of TeamCity Cloud has brought about a paradigm shift: Instead of releasing new features only twice a year, we ca

We want everyone to have the best possible experience with TeamCity, regardless of the size of their team, the complexity of their project, or the technologies they use. In this post, I want to share how we integrate internal feedback from JetBrains teams into our development process. Modern software development practices rely on short iterations and continuous feedback, which allow you to quickly validate your ideas against real users: A common way to run usability research is to recruit a bunch of people, give them a test scenario, and observe their experience while they try to complete yo