As we are working on 4.1 since about 4.0.1, so 4.0.2 is a branch which got only critical bugfixes and urgent improvements.
Generally, you will want to upgrade from 4.0.1 to 4.0.2 if:
- you are using snapshot dependencies and spot build queue growing large with automatically triggered builds of the same build configuration (now we merge them more aggressively)
- you often have builds with lots of failing tests (performance fixes)
- you are using SVN (several fixes incl. performance)
- you are using CVS (fixes in pre-tested commit from IDEA, other)
- you use TFS with large repositories and experience performance issues (we added TFS agent-side checkout, it is a bit experimental, though)
- you are using MSTest reporting (stability fixes)
- you have extra large build numbers (we increased the length from 32 to 256 symbols). In the trunk we also truncate build numbers in web UI to make them usable. This will soon be available in 4.1 EAP
- or if you experienced one of the fixed issues
Need user groups support? Want to move a build configuration from one project to another right from the web UI? These are the features already in development for upcoming TeamCity 4.1. We plan to open EAP for it in a week or so.