Release Notes
Public
8.0.16.3533: Sep 05 2019
New
All platforms - Installers. A new installer named "DVCS Edition" is born! This is the way to go if you are targeting the following layout for your Plastic servers:
* Have a central, on-premise Plastic server in your company.
* Developers have their own, local Plastic server to work with, pushing/pulling from/to central, on-premise server.
* Some developers work directly with the central server.
The advantages of this installer is that you don't have to setup any local Plastic license on every developer machine for its local server.
Also, you can use this installer for your local projects out of the box, with almost zero-conf required.
And still you will be able to push/pull from/to central server.
(Working with a central server is just a matter of entering the server host:port and user credentials. Period).
REMARK: You can access to your local server using the "local" alias as server name, instead of "localhost:8087". Example of local repository spec: my_personal_toolbox@local
New
Windows - Plastic: The new Code Review system now allows you to review a branch, changeset by changeset.
When a developer checks-in often, keeping reviewers in mind, it's helpful to review the branch walking through each changeset. You can read more about this here: https://www.plasticscm.com/book/#_checkin_often_and_keep_reviewers_in_mind
So, we added a new tab that allows you to review a branch, stepping through changeset by changeset:
Note: While reviewing a branch, you can switch between the modes 'Review changeset by changeset' and 'Review entire branch' at any time, adding comments in either of them. Each comment will be displayed in the mode it was added.
Remember, right now, you need to launch the application with "plastic --codereview" to enjoy the new feature.
New
All platforms - Server: Now the server logs the inner exception of the failed calls, so in case of error there is more info available.
Bug
All platforms - all clients: If you deleted a changeset in the plastic-global-config, every operation that needed a file from said global configuration could end up in a stack overflow. This is caused by the following sequence of events:
* Every time the client needs to read a file from the global configuration a hidden, special-purpose workspace is updated to ensure that we have the latest config available.
* Said update operation is typically a fast-update, unless the changeset previously loaded in that workspace is missing from the server.
* If that happens, Plastic must run a full update.
* That full update requires Plastic to check the status of the workspace first.
* And to do so, it needs to read some configuration files from -you guessed it- the plastic-global-config.
* As you might have noticed, this would end up in an infinite loop only stopped by an application crash due to a stack overflow.
Bug
Windows - Plastic: The Update Workspace operation wasn't working fine if there was already another update operation running. It notified you about that and told you to wait until the current operation was finished, but then it continued anyway and the new update operation took over control of the progress panel. The side effect was that the original update operation could be running after the second one finished and you had no way to find out when it was completed. If you closed the GUI at that point you could abort the operation midway -without any warning messages- and the workspace could be left in an inconsistent state. It's fixed now!
Bug
Windows - Plastic: The dialog to resolve file conflicts (non-automatic, with conflicts) sometimes failed with the following exception: "The calling thread must be STA". This only happened if you ran the "Update Workspace" operation in the Workspace Explorer and there were local changes that conflicted with the latest contents of the branch. Now it's fixed.
Note: Users can proceed in three ways when they find themselves in this situation:
* Solve the merge directly when they try to checkin their local changes.
* Solve the merge by clicking the 'View new changes' button in the Pending changes view.
* Solve the merge after clicking the 'Update workspace' button in the Workspace Explorer view.
The merge tool was launched correctly in the first two scenarios to solve the file conflict. It only failed in the last one - which is the least used, by the way!