Home / Companies / Octopus Deploy / Blog / Post Details
Content Deep Dive

Octopus Deploy version changes for 2018

Blog post from Octopus Deploy

Post Details
Company
Date Published
Author
Michael Noonan
Word Count
1,520
Language
English
Hacker News Points
-
Summary

Octopus Deploy has decided to align its versioning strategy with its monthly release schedule, moving from a version number system to a calendar-year-based versioning to enhance predictability and cohesion in its software releases. This change reflects the company's evolution towards a more structured and deliberate approach in software development, emphasizing continuous delivery and incremental updates without altering pricing or licensing. The decision comes from past experiences with ad-hoc versioning that led to internal tensions and a lack of cohesive storytelling in product releases. By adopting a consistent release cadence, Octopus Deploy aims to improve communication, maintain high autonomy among teams, and ensure that each release tells a cohesive story that aligns with a DevOps culture. This strategy underscores the importance of understanding the rationale behind existing practices, akin to the principle of Chesterton's fence, to make informed changes that benefit both the company and its customers.