HMS Product Road Map
===

Version | Status | Target Timeframe | Key Features
------- | -------- | ---------------- | ---------------------------
2026.1  | *WIP* | Q3 2026 | Rebranding+New Features: Implement `hms update` and `hms upgrade` options to initiate a site-wide global topology upgrade without the human admin needing much knowledge of the global topology.  An admin with super access that inherited the Perforce server fleet just yesterday should be able to confidently upgrade the whole thing tomorrow. This is to include all P4 server products (p4d/p4broker/p4p) in the entire global topology. (Swarm management is being considered for a future release). Also: Failover Take 2. Leverage `p4 failover`. HMS manages DFM brokers and knows what machine in the topology to execute `p4 failover` on. HMS now lives in a new home, the //p4-hms stream depot.

Feature Descriptions
---

* **SDP "Tight Ship" 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, P4 itself is used to version the SDP on all HMS hosts. An HMS host is any Perforce server process executes, be it a proxy, broker, master/commit server, replica, edge, Swarm, etc.  The familiar SDP `/p4/common` structure is managed on all hosts from a single server, the p4hms server.  That server in turn uses P4 native DVCS features to simplify the process of updating the SDP from The Workshop, taking advantage of merging power to merge updates to the stock/public SDP into the local environment, which will have local configuration and optional customizations versioned locally.

* **Topology Definition** - HMS provides a data format to describe various aspects of P4 Server components in use.

* **Failover Support for ...** - HMS will provide Scheduled and Unscheduled Failover for the managed P4 components.