Release Notes

Public

Release 6.0.16.1486

Aug 04 2017
New

Gluon: The program file is now a 64-bits executable file.

New

GUI: A new configuration file called 'externaltools.conf' is now available to run actions on the selected objects. It can be included in the plastic-global-config repository at /externaltools/externaltools.conf.

It allows you to define external applications and how they'll receive the selected object properties. This is the syntax:


<objectType>[:<objectType>[...]] | <toolName> | <pathToExecutable> | <args>

- objectType: the name of the targeted object. It can be either item, label, changeset or branch. They can be combined using ':' to separate them.

- toolName: The name of the tool to be displayed in the context menu

- pathToExecutable: Absolute path to the targeted application. Spaces don't need to be escaped or protected.

- args: The arguments line to be passed to the targeted application. There are three currently supported placeholders: @object (replaced with the object name), @repository (replaced with the repository of the object) and @wkpath (replaced with the current workspace path). Please note that the replaced values might contain blank spaces, so they'll probably need to be surrounded with quotes.

Examples:


item | Open with sublime | C:\Program Files\Sublime Text 3\subl.exe | "@object"

label:changeset:branch | Create new code review... | /usr/bin/createcodereview | "@object@@repository" @wkpath

This actions will apear as a new menu item called "External tools" in:

* Branches view context menu

* Changesets view context menu

* Labels view context menu

* History side panel context menu (only GTK & Mac)

This actions will appear appended to the "open" menu item submenu in:

* Items view

* Pending changes view

* History view (only Windows)

New

Cloud: Now, the comment of an object can be updated on the Cloud server.

Bug

Using some SQL backends, the update operation failed when an empty cloaked.conf was added to the repository. Fixed.

Bug

Windows GUI: The #regions in the C# language were not correctly collapsed when the diff option "collapse regions wihtout diffs" was enabled. Now it's fixed.

Bug

The global configuration system always loaded the default server global configuration (i.e. the server defined in the client.conf file) instead of the current workspace repository server. Fixed.

Bug

The Branch Explorer submenu in the branch explorer context menu of selected branches didn't enable the appropriate actions. GTK never allowed to navigate to the branch base and Mac submenu was always empty. 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