Release Notes

Public

Release 8.0.16.3148

Apr 08 2019
New

Command line client: When updating a single item, the cm update command now forces the --cloaked flag by default.

If you specify the item you want to update, then you know for sure what you are doing, so having to add the --cloaked flag is just a hassle.

This means that, for the following directory structure:

src (controlled)
|- file1.txt (controlled / cloaked)
\- file2.txt (controlled)

Then:

> cm update .
(Won't update file1.txt)

> cm update src/*
(Won't update file1.txt)

> cm update src/file1.txt
(Will update file1.txt)

> cm update src/* --cloaked
(Will update file1.txt)

New

Command line. The progress of the cm push/pull/clone commands has been improved so that it shows the number of objects being fetched, like the GUI does, which gives a much better idea of what is going on.

In the example below, you see the tree count together with "fetching trees".


>cm push main@codice@localhost:6060 --package=codice.pkg
Enter credentials to connect to server [localhost:6060]
[#.............................................................]
/ Fetching trees                                         (35735)
Fetching metadata               [###...........................]
Pushing metadata                [..............................]
Introducing data                [..............................]

Bug

Plastic GUI Windows: We have fixed an error in the display of progress messages during replication. A bug was introduced in release 8.0.16.3114 which caused the tool to display some internal strings rather than the nice display strings you are used to.

Internal and public releases

The Plastic SCM development team works in short iterations delivering frequent releases.Our goal is to have at least one new release every week, with new functionalities, bug fixes and performance tweaks.

Every 'weekly' release is not published to our customers, but we like to detail each of them in the release notes so users can easily follow what we achieved on every short iteration.

The releases marked with the word "public" are the ones we do publish on the website. The ones marked as "internal" are the releases we create in-house to keep the project moving week after week.

Version numbering

Starting in Plastic SCM 4.0 the version numbering schema has been modified:

  • major.minor.compatibility.buildnumber

  • Sample: 5.0.44.511 means:
    • 5 -> major release number
    • 0 -> minor release number
    • 44 -> compatibility -> all clients and servers with "44" in the compat number are compatible, even if the build number changes
    • 511 -> internal build number