Downloads

What are the naming rules for builds?

Starting from 3 January 2012 the version number rules were changed.

• The first digit changes, when a build with major requirements is released.

• The second digit changes, when there are minor or small requirements introduced.

• The third digit is other than zero for bug fixes only and refactorings releases. This is a combination of (composite number):

  • 00001 - contains business logic bug fixes
  • 00100 - contains performance enhancements
  • 10000 - contains architectural refactorings

• The last digit just enforces uniqueness.

Examples:
1.2.20301.1234 - there was one release with major requirements, 2 releases with small requirements, 2 releases with architectural changes, 3 releases with performance enhancements and 1 release with business logic bugs. It doesn't mean, there were 6 bug fixes releases. A single one could simultaneously include all these types.

Version 1.1 (1.0.00001.0 according to new numbering)

Includes bug fixes only. For the complete list see here.

Version 1.0

The very first version 1.0 is released. It includes the following features:

• A distributed network is maintained based on auto-discovery (UDP broadcasts) and on predefined list of addresses.
• Update of this network is performed automatically upon placing a folder with new version onto the server (unfortunately this is not yet done on fly. So you need the network to be free before performing updates).
• Tests are run on all agents simultaneously. The smallest "test unit", which can be distributed among agents is NUnit's test suite (TestFixture). Upon completing the results are merged on server and stored.
• There is a dashboard available to monitor the status of server and agents.