IHS
Markit would like to inform you that we do not plan to offer further
improvements around direct integration between EDM and external version control
systems, such as TFS or SVN.
In
2019, we intend to move towards a standard that will better serve our customers.
This will involve EDM exporting and storing component definitions in the file
system, whereby any external source control provider can access them, enabling
branching and merging capabilities outside of EDM. An import process would be
created to import and synchronize the definitions back into the EDM database
when needed from the file system.
While
we will continue to support existing functionality that is already available in
the EDM thick-client application, such as direct integration with TFS 2015 or
SVN 1.8, there are no plans to add support for additional versions such as TFS
2018 or SVN 1.9.
Going
forward, we are encouraging our customers to use our internal database version
control system which provides maximum flexibility and control over version
control integration. As of version 19.1, EDM's native database version control
will still be leveraged to store individual historical version changes per
component via the thick client even. Further database version control
improvements have been made in the latest versions of EDM v11.5 (11.5.48.0+) and EDM v17.1 (17.1.123.2+) which can be reviewed in the release notes.
