Release Notes

Public

Release 6.0.16.960

Mar 31 2017
New

Windows, Linux (GTK) and Mac OS GUIs: Now, the Plastic SCM GUI will measure the performance while looking for pending changes on your workspace. If the GUI detects that the performance of the operation is not as good as expected, depending on the cause, it will give you advice on how to improve it.

New

CLI tools: Now, the cm CLI tool will measure the performance of the status operation. If it detects that the performance of the operation is not as good as expected, depending on the cause, it will give you advices about how to improve it (except if the --machinereadable or --xml flags are set).

New

Configuration files: the performance warnings can be enabled through the client.conf file, adding the following key:

<ShowPerformanceWarnings>yes</ShowPerformanceWarnings>

New

Linux (GTK) and Mac OS GUIs: The changesets view context menu includes a new option: "Diff with another changeset". It enables users to select a changeset in a context dialog and diff its contents with the selected changeset. This menu option is also available in the Branch Explorer when a single changeset is selected.

New

Linux (GTK) and Mac OS GUIs: The branches view context menu includes a new option: "Diff with another branch". It enables users to select a branch in a context dialog and diff its contents with the selected branch. This menu option is also available in the Branch Explorer when a single branch is selected.

Bug

Linux (GTK) and Mac OS GUIs: Changing the display options or the date filter in the Branch Explorer view of a workspace window caused the rest of the workspace windows to load that configuration without notice or updating the GUI controls. Fixed.

Bug

Cloud and Jet: Checkin operation with 'added' items and 'keep items locked' preference enabled failed. Now it's fixed.

Bug

The P4 sync was failing with directories with the FileSystem permissions changed. Fixed.

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