|Version||Status||Target Timeframe||Key Features|
|2019.1||WIP||Early March, 2019||Back to a standalone project, bringing hardening updates and fixes.|
|w/SDP||Released||From 2016-2019||Primarily hardening and bug fixes.|
|2016.1||Released||September 2016||SDP Version Management, Topology Definition, Failover Support for p4d, p4broker, Replication Normalization, Simplified Replica/Edge Server Setup, Helix Component Status Visualization|
SDP Version Management - A necessary step on the path to successful automation across multiple machines is to solve basic version management challenges for the SDP itself. Essentially, Perforce itself is used to version the SDP on all HMS hosts -- hosts on which any Perforce server process executes, be it a proxy, broker, master server, Swarm, P4Search, etc. The familiar SDP
/p4/common structure is managed on all hosts from a single server, the HMS server. That server in turn uses Helix DVCS features to vastly simplify the process of updating the SDP from The Workshop, taking advantage of Perforce merging power to merge updates to the stock public SDP into the local environment, which will have customizations versioned locally.
Topology Definition - HMS provides a data format to describe various aspects of Helix server components in use.
Failover Support for ... - HMS will provide Scheduled and Unscheduled Failover for the specified components.
Replication Normalization - HMS will not support all possible replication options. Part of its value is that it will only the most useful replica types and usage options, based on Consulting experience working with customers, distilling the myriad potential options (all of which are useful in some context). The normalization includes defining naming conventions for naming server specs that readily convey their usage.
mkrep.sh -t fr -s bos -r bos-helix-02