New versioning schema

Tuesday, May 22, 2012 0 Comments

Since we released Plastic SCM 4.1 a few weeks ago, we have introduced a new numbering schema. Our goal is to make it easier to understand especially concerning compatibility between client and servers.

The following picture explains what the 4 numbers we use to name a version (e.g. means:

  • Major: The major version number (good for marketing and customers)
  • Minor: for identification purposes (4.0, 4.1, 4.2 and so on)
  • Common: identifies compatibility between client and server (inside the same major version!). It will be the number in commontypes. We are going to make it VISIBLE so customers understand when a version is compatible.
  • BuildNumber: just the number of the build -> it is a unique number that always grows and doesn’t mean anything… just how old and cool we get as we reach 200, 300, 500 or 1000!!! We keep it because it rocks

    So, in order to understand if the new version you’re going to download is fully compatible with yours, check the following:

    Go to your “about form” and check the 3rd number: is it the same as the third one in the version you’re about to download? Then the new version is fully compatible and you can update clients and servers separately, they’ll continue to run.

    If they don’t match, it means you’ve to upgrade both clients and servers, since your current version and the new one are not compatible.

    We try to minimize compatibility changes, but sometimes we’ve to make changes on the communication API and we break compatibility.

  • We develop Plastic SCM, a version control that excels in branching and merging, can deal with huge projects and big binary assets natively, and it comes with GUIs and tools to make everything simpler.

    If you want to give it a try, download it from here.

    We are also the developers of SemanticMerge, and the gmaster Git client.

    0 comentarios: