Plastic SCM 4.1.10.397 is out!!!

Monday, February 11, 2013 0 Comments

Reading Plastic SCM releases notes you are the first to know what’s new with upcoming releases.

Now, we present Plastic SCM 4.1.10.397 release or “Tanger” release is the alternative name. A new release kindly delivered!!

You may also want to check out all release notes. You can find them here.

Remind, download the latest Plastic SCM version from our web page.

The new updates for Plastic SCM enhance the most relevant new features and bug fixes.

Features

Plastic SCM Mylyn installer

The biggest added, in my opinion is this: Mylyn for Eclipse is included in the Plastic SCM installer. You can grab it now from Plastic SCM download page.

For an up-to-date list of the third-party products and versions supported, please consult our third-party tools compatibility matrix page.

Preferences

One of the options in Plastic SCM “Preferences” is allow (or not allow) to switch /update a workspace that it contains changed items.

This option has been moved from “guiclient.conf” file (GUI configuration) to “client.conf” (common configuration).

This value will be upgraded the first time that Plastic SCM 4.1.10.397 is loaded.

Furthermore, this preference can still be changed from GUI. You can select “Preferences” on the left hand, then click on “Other options” and check one of the following options under “Behavior when trying to switch/update the workspace with changed item” option:

  • Allow
  • Allow, showing a warning
  • Do not allow, showing an error

You will see something similar to figure below:


BUGS

Server Stats Logging

The server stats logging was failing in some concurrency scenarios, for example when the call user wasn’t set yet. Fixed!

Tree 2D

There are two bugfixes about Tree 2D:

  • There was a stack overflow exception when the main branch has a long history.
  • The changeset number was cut when drawing the vertical layout.

Method history

In Linux, a null error was raised when a view was opened, from the “Annotate View” as usual. It happened when setting the value of a DataGridViewCell object in Mono 2.6.x. Fixed

Hope you enjoy our new release!!

0 comentarios: