Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

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

We also code SemanticMerge, and the gmaster Git client.

New versioning schema

Tuesday, May 22, 2012 Pablo Santos 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.

    Pablo Santos
    I'm the CTO and Founder at Códice.
    I've been leading Plastic SCM since 2005. My passion is helping teams work better through version control.
    I had the opportunity to see teams from many different industries at work while I helped them improving their version control practices.
    I really enjoy teaching (I've been a University professor for 6+ years) and sharing my experience in talks and articles.
    And I love simple code. You can reach me at @psluaces.
  • 0 comentarios: