# Product Roadmap for SDP 2024.2 Release ## Release Schedule The target for SDP 2024.2 is Mid Q4 2024. SDP generally ships about 10 business days after the corresponding Helix Core (P4D) Server release. ## Expected Features These features are features we expect to include in the SDP 2024.1 release. | Job |Title|Type|Component|Notes| |-------|-----|----|---------|-----| | [SDP-1154](https://perforce.atlassian.net/browse/SDP-1151) | upgrade.sh: Fixed message indicating why 2nd journal rotation skipped. | B | core-unix | | [SDP-1113](https://perforce.atlassian.net/browse/SDP-1113) | Added '-p4config' option to mkrep.sh to target arbitrary p4d server. | F | core-unix | | [SDP-1093](https://perforce.atlassian.net/browse/SDP-1093) | Script to enable and disable Broker. | F | core-unix | | [SDP-1079](https://perforce.atlassian.net/browse/SDP-1079) | Make live_checkpoint.sh work on replicas/edges. | F | core-unix | | [SDP-1050](https://perforce.atlassian.net/browse/SDP-1050) | Upgrade p4dstate.sh, p4pstate.sh, and p4brokerstate.sh to be SDP-aware. | F | core-unix | | [SDP-1043](https://perforce.atlassian.net/browse/SDP-1043) | mkdirs.sh does not detect invalid p4d or similar binaries in sdp/helix_binaries dir. | B | core-unix | | [SDP-811](https://perforce.atlassian.net/browse/SDP-811) | Eliminate Python 2.x dependency in SDP. | F | core-unix | | [SDP-786](https://perforce.atlassian.net/browse/SDP-786) | Account for impact of NFS sharing on failover procedure. | D | core-uinx | | [SDP-568](https://perforce.atlassian.net/browse/SDP-568) | Standardize logging method to 'exec & tee'. | F | core-unix | | | [SDP-530](https://perforce.atlassian.net/browse/SDP-530) | Make all UNIX SDP scripts conform in style for logging, -h/-man flags. | F | core-unix | | | [SDP-361](https://perforce.atlassian.net/browse/SDP-361) | Make p4d_base refuse to start p4d if server.id value is DISABLED. | F | core-unix | | [SDP-38](https://perforce.atlassian.net/browse/SDP-38) | checkpoint.log contains cruft from earlier failed run. | B | core-unix | Note: JIRA issue links are not publicly accessible. For more information, contact support-helix-core@perforce.com.