Release Notes

Public

Release 7.0.16.2679

Oct 18 2018
New

DevOps: The server will ensure that the plug configurations linked from a mergebot configuration are started when you create a new mergebot configuration or you edit a mergebot configuration that was running at that point. This will also happen when you start a mergebot configuration!

New

Windows GUI: Added a close action in the Branch Explorer's diagram legend.

New

All GUIs and CLI: Server side merge is now enabled by default. You can learn more about server side merges here: http://blog.plasticscm.com/2018/03/workspace-less-merge-to.html

New

We reduced the amount of debug log generated by the replication operation. The server no longer logs replicated trees, which were the reason why replication logs grew up to 40 GB in some cases.

Bug

DevOps: merge failed with the error "Attempted to divide by zero." under certain circumstances when the file conflicts were resolved using the semantic merge. Now it's fixed.

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