Release Notes
Public
7.0.16.2006: Feb 28 2018
New
From now on, the merge tools included with plastic will have their own configuration. Before they were using both config files, the client.conf and the mergetool.conf. Now, they will get the configuration only from the mergetool.conf file. The configuration moved is:
* language=es
* fipscompliant=true
* stacktrace=true
Please add these keys to your mergetool.conf file in case you want to change those values.
Bug
OS X GUI: The merge view opened the branch explorer properties in the side panel when a merge finished. It was a minor detail, but it could be slightly confusing to users. Fixed.
Bug
OS X and Linux GUI: After processing a merge, the hint message at the bottom of the merge view was wrong. It informed that the merge search finished without results, instead of notifying that the merge was successfully completed. Fixed.
Bug
Workspace update (you know, switching to a different branch or cset) had an issue if a directory or file was locked (i.e. directory in use). Now the operation keeps the locked item as private (or out-of-date) and goes on updating the rest of the workspace.
Example: you have a console open in src/server and then you switch back to changeset where src was named "code". Before, the operation failed and the workspace was dirty. Now it works great, leaving just src/server as private. In fact, if you later go back to the initial changeset, the private is reused.
Bug
Windows: Sync with Git feature didn't support the TLSv1.2 cryptographic algorithm for HTTPS, so synchronizing against some providers (e.g. GitHub) failed. Fixed.
REMARK: Still pending to fix this issue for non-windows plastic applications.