Release Notes

Public

8.0.16.3750: Nov 18 2019

New

All platforms - trunkbot: We felt that your life would be easier if the trunkbot could define the expected status attribute values as the list of default values. So, we did that! The trunkbot will write a new line defining that list of default values when it creates the status attribute. Remember: this only happens if the status attribute doesn't exist on bot startup. The trunkbot won't update comments of existing attributes.

New

All platforms - multilinerbot: Just as we did with the trunkbot, we improved the multilinerbot so it write the list of expected status attribute values as the list of default values for the status attribute. Remember: this only happens if the status attribute doesn't exist on bot startup. The multilinerbot won't update comments of existing attributes. Oh, and this just applies to the status attribute, not the one to define the merge destination branches!

New

All platforms - Command line client: We improved the update command startup time. Empty or small updates are now 14% faster than before.

New

All platforms - Command line client: We added the option '--skipchangedcheck' to the update command. The update checks for pending changes before starting. This option skips looking for locally changed files. This way you will save time using this option if you always checkout the files before you change them.

New

Windows - Plastic: the focus is now correctly set on the server field of the configuration panel when launched using "plastic --configure"

New

macOS, Linux - Plastic, Gluon: We unified the contextual menus in the Pending Changes view as much as possible - both for Plastic and Gluon. Now finding the features you use the most is easier when switching applications.

But this change brings other goodies too! For example, now you can check a file's history, and annotate it, right from the Pending Changes. We also added support to change cloaked.conf in Plastic, and hidden_changes.conf in Gluon.

Remember that Gluon and partial workspaces don't consider cloaked.conf file. That's why you can't configure it from Gluon.

New

macOS - Plastic: The GUI now shows a notification in the toolbar when the changeset you are working on no longer exists. This can happen if a colleague deletes that changeset.

This helps users returning to a valid configuration by updating the workspace. The notification looks like this - click on "Update" and you are good to go!

New

macOS - Plastic: We improved the message for the Incoming Changes view. It now explains that you only need to update the workspace to synchronize the metadata when your changes match the ones in the new head of the branch.

New

macOS - Plastic: We added a tooltip in the notification bar for the incoming changes to explain the current scenario.

The available scenarios are:

* There are new changes in the branch that you can preview and download.

* There are new changesets that conflict with your current changes.

* The changeset you were working on no longer exists. Click the "Update" button to return to a valid configuration.

New

All platforms - Gluon: removed "Show hidden files" from the check-in options, since it is only relevant to Plastic.

New

All platforms - Plastic, Gluon: The Similarity Percentage slider (in Pending changes -> Options -> Move detection) now correctly disables when the Find Moved option is deselected.

New

All platforms - Server: On-premises servers now support global lock rules! Bear in mind that global lock rules will be used for all repositories unless there are repository-specific rules that apply to them. They aren't merged, but replaced!

So, if you'd like to override the global lock rules for one of your repos, simply create lock rules for it. If you leave them empty, no rules will apply.

New

All platforms - WebAdmin: We added a new block to store the global rules. And now you'll have auto-complete features to enter the repository names for repository-specific rules! Isn't that nice?

New

All platforms - Proxy server: We added the caller IP and user name in the log line after the GetObjectsData call. You can now see who's causing trouble!

Now the log is as follows:

Proxy - Request:     39. Type: downl. Files requested:   10. Cache misses:    10. Total time:    16 ms. Downloaded: 3.78 Mb from default@localhost:8084. Total returned: 3.78 Mb. IP: 127.0.0.1. User: 'pablo'.

New

Windows - Plastic: The annotate pane could end up misaligned with the code pane by up to a line due to the way we were synchronising the two panes. We changed the way we do this, and now we have pixel-perfect alignment.

Bug

Windows - Plastic: fixed a bug in Cloud Edition where issue tracker settings were not being saved correctly.

Bug

All platforms – Proxy Server, Client: Fixed an issue downloading data from the cloud that impacts the performance. The issue was introduced on the release 8.0.16.3725. If you are using the release 8.0.16.3725, please upgrade.

Bug

All platforms - Client, Server: The Incoming Changes operation sometimes left writable Xlinks as pending changes. This issue only affected Xlinks with more than one expansion rule. It took place when the server changes contained the first changes in the current branch under the Xlink.

Bug

All platforms - Plastic, Command line client: The client didn't detect Xlink deleted-changed conflicts in some merge scenarios. This happened when the current user had pending changes under a Xlink in their workspace. Additionally, the source contributor had deleted it. Now the Plastic clients do detect the conflict.

Bug

All platforms - Plastic, Command line client: The merge operation failed in a complex scenario. It involves merges whose source changes modify the Xlink path. At the same time, the merging user has pending changes in their workspace under that Xlink.

This is an example scenario that reproduced the issue:

* First, Alice is working in branch '/main'. She renames the '/physics' directory to '/effects' and adds a writable Xlink. She checks in these changes.

* Then, Beth checks out the file '/physics/water.cs' in her current workspace.

* Finally, using the same workspace, Beth starts a merge from '/main' into her current branch.

At this point, the merge operation failed with this error message: "Item 55 could not be found...".

Bug

All platforms - Server: The Incoming Changes operation left the previous version as deleted when you replaced a Xlink in the server. Now it's fixed.