Julia Programming Language Details Its Official Release Process

The Julia programming language community has published a comprehensive guide detailing its software release process to clarify procedures for both internal developers and external users. While Julia adheres to semantic versioning standards, this documentation fills gaps regarding specific workflows, risk management, and version types. The article distinguishes between patch releases, which occur monthly and contain only bug fixes and low-risk improvements, and minor releases, which happen every four months and may include new features or internal refactorings. Major releases and long-term support structures are also outlined. The guide emphasizes the use of PkgEval, an automated testing tool, to ensure that changes do not break existing packages in the ecosystem. It further defines user personas based on risk tolerance, helping developers choose appropriate versions for their needs. By consolidating information previously scattered across forums and chat channels, this post aims to standardize understanding of Julia's development rhythm. The authors suggest this document may become an official reference if well-received, providing transparency on what changes are permissible in each release stage and how pre-release versions function within the broader maintenance strategy.