Temporal V1 Release

3/29/2024

This post announces the release of Temporal Server version 1.23.0, highlighting changes such as a proto library, new reserved search attributes, and depreciations. It also mentions the public preview release of a Terraform provider for Temporal Cloud to manage Namespaces and the public preview availability of Workflow History Export. Updates to the PHP SDK (2.8, 2.8.1) with Workflow Update support, Go SDK (1.26) with Typed Search Attributes, and Java SDK (1.23) with bug fixes and history JSON format changes are also noted.

9/29/2020

This post announces the official V1 production release of Temporal, a significant milestone for the platform. It details the implications of V1, including the establishment of a backward compatibility era for public APIs and the introduction of a deprecation policy. A specific technical detail mentioned is the improvement in shard ID hashing, which can lead to a temporary increase in resource usage during in-place cluster upgrades, though without any risk of data loss. The post also categorizes certain features (Archival, Cross DC Replication, Batch Operations, Dynamic Config, Elasticsearch searchable attributes) as 'experimental' and outlines the versioning strategy for clients and servers, including the introduction of client headers for compatibility checks.

9/18/2020

This post announces that Temporal V1 is code complete for its stabilization effort, with all required tests now running in the pipeline. Several components have been stabilized, and identified bugs are being fixed. Features designated as 'experimental' for the V1 release include Archival, Cross Data Center Replication, Batch Operations (signal, terminate, cancel), Dynamic Config, and dynamic management of searchable attributes with Elasticsearch. The post links to specific GitHub pull requests for bug fixes related to workflow execution history page size, workflow creation reliability after shard movement, and simultaneous signal/start reliability.

9/4/2020

This post details the stabilization progress for Temporal V1, focusing on deployment infrastructure improvements (dedicated Cassandra cluster, isolated Cassandra nodes from Temporal server for perf testing), completion of non-failure bench scenarios, initial work on failure scenarios (integration with Gremlin pending), validation of component failure/resumption tests, and ongoing development of backlog scenarios. It highlights a decreasing trend in newly discovered bugs, indicating successful stabilization efforts.

8/7/2020

This post details the final stages of code completion for the JavaSDK, including a significant refactor and the submission of a PR for review. It also announces the team's shift in focus to stabilization efforts for Temporal V1, outlining key areas of investment: automated deployment infrastructure using Concourse for CI/CD pipelines, rigorous scale testing to ensure graceful load handling, and comprehensive failure testing to guarantee system resilience and workflow progress during failures. The post reiterates the commitment to backwards compatibility and schema compatibility, while strongly advising against using the current release in production due to the ongoing stabilization process.

7/31/2020

This update announces that the Temporal server and GoSDK are code complete for V1, with no further breaking API/code changes expected for these components. The JavaSDK is delayed until the following week. The primary focus has shifted to stabilization, with a commitment to releasing V1 only when stability is confirmed. Breaking schema changes are not expected post-V1. A testing and validation plan for V1 will be shared the following week.