Release Notes

Public

Release 7.0.16.2105

Apr 06 2018
New

Windows GUI: we made some changes in the tabs of the main window, including resizing and rewording.

We made the tabs adjust better to the title, so more text is readable now.

We also made a big change: "Items view" is gone and now we call it "Workspace Explorer". Hope this won't annoy old users, but we think "items view" is too abstract for many newcomers.

This will solve this User Voice Reduce tab text to fit within tab shapes

Now, a story about "items view": back in 2005 we named versioned files and directories "items". In fact, each version of a file or directory was called "revision" but in order to refer to the abstract object itself we called it "item". See what I mean? An item can have many revisions, each of them containing data (contents of a given file or the directory entries if the item is a directory). Item/revision is like class/object. We had this "item" concept so deep in our minds, that we kept the "design name" in the GUI. And it survived 13 years :-) Now it almost sounds ridiculous to us, but for a long time we didn't almost pronounce file&directory but "item". Fortunately, now we simply try to make things simpler for users :-)

Bug

When you try to cancel a replication operation that failed just while it was starting, the cancel failed with the error 'AssertFalse has found a positive condition'. Now it's fixed.

Bug

Jenkins plugin: In Blue Ocean, if a build included multiple changesets, only the first one was rendered in the details. Also, the info for the commit and timestamp columns were not filled. Fixed.

Bug

The merge-to operation failed under some circumstances when the merge included at least a deleted directory and a moved directory. This could happen only when the moved directory contained one item involved on the merge. Now it's fixed.

Bug

OS X GUI: A null value message was shown, in rare circumstances, during the merge. It didn't have any effect on the operation. It was only an issue in the progress notification. Now, it's fixed.

Public

Release 7.0.16.2095

Apr 04 2018
New

Windows GUI: we have done some improvements in the merge window after the new "merge-to" feature was implemented:

* New title for "merge-to" with conflict resolution.

* Handle the error when the server doesn't support thew new merge-to.

Bug

SemanticSCM: The semantic differences reported a parsing problem on launch when the source code parser was terminated. Fixed

Public

Release 7.0.16.2082

Mar 27 2018
Bug

Linux GUI: Fixed an index out of bounds exception when clicking the last line of an annotated file.

Public

Release 7.0.16.2077

Mar 26 2018
New

New feature in preview: server-side merge (or "merge-to" with conflict resolution, if you prefer).

To enable it: add this in your client.conf:


<ServerSideMergeEnabled>yes</ServerSideMergeEnabled>

If you have been using Plastic for a while, chances are you are familiar with the "merge-to" feature. It lets you do "workspace less" merges. Like, you don't even have a workspace, but you can merge "main/task127" into "main".

But, merge-to had a big restriction: it only worked if there were no manual conflicts. As soon as a file had a conflict (even a simple one that could be fully automated), or a directory was in conflict, merge-to stopped.

Now this changed, and all type of conflicts, including file merges, can be resolved in merge-to.

The motivation behind the change? We are all moving towards more automated workflows where every single branch is tested before being merged. So, under that way of thinking, testing in your workspace first is not always necessary. We changed our minds here because, for years, we thought it was good to build and test your code locally prior to checkin the result of the merge, but DevOps and automation are changing all that, so now we feel confident of this merge-to with conflict resolution approach.

The feature is in preview at this point because is just out from the oven, but it will be enabled by default soon.

New

Linux GUI (Gtk): Now, you can create new attributes directly from the GUI. To do so, click on the "Apply attributes" button on the right of the Branch Explorer, and click on the "Create" button next to the attribute list.

Public

Release 7.0.16.2074

Mar 23 2018
New

Linux GUI: annotate is now ready (blame). Just right click a controlled item in the workspace explorer view, and select the "annotate" menu item.

New

Linux GUI: Load only the last 500 values of an attribute due to a performance issue with the dropdown control. Otherwise it takes forever to load. We tested with 30k values (reported by a customer) and it freezed for more than 30 secs.

New

GUI client apps (Plastic, Gluon and Mergetool) will now leave rolling log files in $HOME\.plastic4\logs folder. In case of windows, the folder path is %LOCALAPPDATA%\plastic4\logs\.

Those apps will generate an info log file with relevant telemetry and another log file with more details and debug info.

New

Server: Add support for OpenLDAP with the anonymous access disabled.

New

Windows GUI, Gluon, Linux and OS X: Remember the workspace base path between sessions. By default, PlasticSCM proposes the $HOME/wkspaces directory to create new workspaces. Now, if the user changes this directory, Plastic will remember the base path and will propose it for the next time.

New

TeamCity plugin: The auto-merge capability is now able to merge branches when the file conflicts are automatic. Before the fix, any file conflict (automatic or not) rejected the merge.

Bug

Changesets can't be deleted when there are shelves depending on them. However, the Jet backend incorrectly allowed this to happen. As a result, the dangling shelves became unusable (they couldn't be applied nor viewed). We've fixed this so this scenario of the 'delete changeset' operation won't happen anymore under Jet.

Bug

Jenkins plugin: Reduced the number of duplicated builds that can happen using the Plastic SCM plugin. Now, the scm polling takes into account the current build avoiding to start a new build for the same changeset.

Bug

Linux GUI: Fixed a "collection modified" exception when closing the annotate view.

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