From 14f35c469ff912a3520caeb5515b88c0714bfb0e Mon Sep 17 00:00:00 2001 From: Luke Massa Date: Sun, 2 Feb 2025 23:24:31 -0500 Subject: [PATCH 1/5] docs: Atlantis 1.0 blog post --- runatlantis.io/.vitepress/sidebars.ts | 10 ++++++++++ .../blog/2025/introducing-atlantis-1.md | 18 ++++++++++++++++++ 2 files changed, 28 insertions(+) create mode 100644 runatlantis.io/blog/2025/introducing-atlantis-1.md diff --git a/runatlantis.io/.vitepress/sidebars.ts b/runatlantis.io/.vitepress/sidebars.ts index 9afc20f780..b3f6a43e3b 100644 --- a/runatlantis.io/.vitepress/sidebars.ts +++ b/runatlantis.io/.vitepress/sidebars.ts @@ -101,6 +101,16 @@ const en = [ link: "/blog", collapsed: false, items: [ + { + text: "2025", + collapsed: true, + items: [ + { + text: "Introducing Atlantis 1.0!", + link: "/blog/2025/introducing-atlantis-1" + }, + ] + }, { text: "2024", collapsed: true, diff --git a/runatlantis.io/blog/2025/introducing-atlantis-1.md b/runatlantis.io/blog/2025/introducing-atlantis-1.md new file mode 100644 index 0000000000..5363028efe --- /dev/null +++ b/runatlantis.io/blog/2025/introducing-atlantis-1.md @@ -0,0 +1,18 @@ +--- +title: Introducing Atlantis 1.0! +lang: en-US +--- + +# Atlantis User Survey Results + +The core team is excited to announce the release of Atlantis 1.0.0! This release is many years in the making, and we're excited to be bringing Atlantis + +## Questions + +### What should we expect from this release? + +We don't expect 1.0.0 to be any different than any of our "minor" releases starting with `0`. It's merely an indication that we believe the product is stable enough to warrant 1.0 release. + +### When do we expect Atlantis 2.0? + +There are no immediate plans to release Atlantis 2.0, nor do we think it will never happen. We are roughly following semver guidelines described [here](https://semver.org/), which note that the major version should be incremented if "backward incompatible changes are introduced to the public API". (TODO: What does that mean for Atlantis?). If that ever happens, we reserve the right to release Atlantis 2.0. But releasing 1.0 is an indication of our commitment to stability and maintaining backwards compatibility. \ No newline at end of file From 435ff5139c273674f8be7ee4389b8a82acff52f9 Mon Sep 17 00:00:00 2001 From: Luke Massa Date: Wed, 5 Feb 2025 18:28:22 -0500 Subject: [PATCH 2/5] Update --- runatlantis.io/blog/2025/introducing-atlantis-1.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/runatlantis.io/blog/2025/introducing-atlantis-1.md b/runatlantis.io/blog/2025/introducing-atlantis-1.md index 5363028efe..27925876e7 100644 --- a/runatlantis.io/blog/2025/introducing-atlantis-1.md +++ b/runatlantis.io/blog/2025/introducing-atlantis-1.md @@ -1,5 +1,5 @@ --- -title: Introducing Atlantis 1.0! +title: Introducing Atlantis 1.0.0! lang: en-US --- @@ -11,8 +11,11 @@ The core team is excited to announce the release of Atlantis 1.0.0! This release ### What should we expect from this release? -We don't expect 1.0.0 to be any different than any of our "minor" releases starting with `0`. It's merely an indication that we believe the product is stable enough to warrant 1.0 release. +We don't expect 1.0.0 to be any different than any of our "minor" releases starting with `0`. It's merely an indication that we believe the product is stable enough to warrant 1.0.0 release. -### When do we expect Atlantis 2.0? +### When do we expect Atlantis 2.0.0? + +There are no immediate plans to release Atlantis 2.0.0, nor do we think it will never happen. We are roughly following semver guidelines described [here](https://semver.org/), which note that the major version should be incremented if "backward incompatible changes are introduced to the public API". (TODO: What does that mean for Atlantis?). If that ever happens, we reserve the right to release Atlantis 2.0.0. But releasing 1.0.0 is an indication of our commitment to stability and maintaining backwards compatibility. + +### How will we decide whether to increment major, minor, or patch for a given release? -There are no immediate plans to release Atlantis 2.0, nor do we think it will never happen. We are roughly following semver guidelines described [here](https://semver.org/), which note that the major version should be incremented if "backward incompatible changes are introduced to the public API". (TODO: What does that mean for Atlantis?). If that ever happens, we reserve the right to release Atlantis 2.0. But releasing 1.0 is an indication of our commitment to stability and maintaining backwards compatibility. \ No newline at end of file From df31bfe1efc36be12a347c56669c740629b1e9de Mon Sep 17 00:00:00 2001 From: Luke Massa Date: Sat, 8 Feb 2025 16:02:20 -0500 Subject: [PATCH 3/5] Updating text --- .../blog/2025/introducing-atlantis-1.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/runatlantis.io/blog/2025/introducing-atlantis-1.md b/runatlantis.io/blog/2025/introducing-atlantis-1.md index 27925876e7..64cd884702 100644 --- a/runatlantis.io/blog/2025/introducing-atlantis-1.md +++ b/runatlantis.io/blog/2025/introducing-atlantis-1.md @@ -5,17 +5,28 @@ lang: en-US # Atlantis User Survey Results -The core team is excited to announce the release of Atlantis 1.0.0! This release is many years in the making, and we're excited to be bringing Atlantis +The core team is excited to announce the release of Atlantis 1.0.0! This release is many years in the making, and we're excited to be bringing Atlantis into this next chapter. ## Questions +### Why now? + +Atlantis has reached level of maturity, both as a product as well as a project, that justifies the designation that comes with a stable 1.0.0 release. + +One technical issue that this release solves is that, right now, when the Atlantis team publishes a new feature release by incrementing from `0.X.Y` to `0.{X+1}.0`, it is impossible to tell if there are breaking changes in the release without reading the release notes. In a post-1.0.0 world, breaking changes will always be accompanied by a bump in the major version (see below), hence the version number will encode more meaning. + ### What should we expect from this release? -We don't expect 1.0.0 to be any different than any of our "minor" releases starting with `0`. It's merely an indication that we believe the product is stable enough to warrant 1.0.0 release. +We don't expect 1.0.0 to be any different than any of our "minor" releases starting with `0`. It is primarily an indication that we believe the product is stable enough to warrant 1.0.0 release, and to show our commitment to both stability and backwards compatibility. -### When do we expect Atlantis 2.0.0? +### Will there be do an Atlantis 2.0.0? -There are no immediate plans to release Atlantis 2.0.0, nor do we think it will never happen. We are roughly following semver guidelines described [here](https://semver.org/), which note that the major version should be incremented if "backward incompatible changes are introduced to the public API". (TODO: What does that mean for Atlantis?). If that ever happens, we reserve the right to release Atlantis 2.0.0. But releasing 1.0.0 is an indication of our commitment to stability and maintaining backwards compatibility. +There are no immediate plans to release Atlantis 2.0.0, nor do we think it will never happen. We are roughly following semver guidelines described [here](https://semver.org/), which note that the major version should be incremented if "backward incompatible changes are introduced to the public API". (TODO: What does that mean for Atlantis?). If that ever happens, we reserve the right to release Atlantis 2.0.0. ### How will we decide whether to increment major, minor, or patch for a given release? +We are roughly guided by the recommendations [here](https://semver.org/), which roughly say that bug fixes go in patch releases, feature changes go in minor releases, and backwards incompatible changes go in major releases. + +As mentioned above, right now backwards incompatible changes are included together with "normal" releases. As we get experience separating these, we will develop a more clear understanding of what it means for a change to be backwards incompatible. For now here are a few guidelines: +- Changes to server or repo config such that previously specified valid flag and configuration immediately fail +- Changes to behavior like when applies and plans are run, except when gated by a new flag or setting \ No newline at end of file From 11d5b3add5a19d00aac4e896641c151f61559a87 Mon Sep 17 00:00:00 2001 From: Luke Massa Date: Sat, 8 Feb 2025 20:44:30 -0500 Subject: [PATCH 4/5] Use 1.0.0 consistently --- runatlantis.io/.vitepress/sidebars.ts | 4 ++-- ...ntroducing-atlantis-1.md => introducing-atlantis-1-0-0.md} | 0 2 files changed, 2 insertions(+), 2 deletions(-) rename runatlantis.io/blog/2025/{introducing-atlantis-1.md => introducing-atlantis-1-0-0.md} (100%) diff --git a/runatlantis.io/.vitepress/sidebars.ts b/runatlantis.io/.vitepress/sidebars.ts index b3f6a43e3b..21a00531a1 100644 --- a/runatlantis.io/.vitepress/sidebars.ts +++ b/runatlantis.io/.vitepress/sidebars.ts @@ -106,8 +106,8 @@ const en = [ collapsed: true, items: [ { - text: "Introducing Atlantis 1.0!", - link: "/blog/2025/introducing-atlantis-1" + text: "Introducing Atlantis 1.0.0!", + link: "/blog/2025/introducing-atlantis-1-0-0" }, ] }, diff --git a/runatlantis.io/blog/2025/introducing-atlantis-1.md b/runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md similarity index 100% rename from runatlantis.io/blog/2025/introducing-atlantis-1.md rename to runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md From b291b8871a46a6b46e91993725152fa8cdab3078 Mon Sep 17 00:00:00 2001 From: Luke Massa Date: Sat, 8 Feb 2025 20:45:54 -0500 Subject: [PATCH 5/5] Fix --- runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md b/runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md index 64cd884702..726e49b5a4 100644 --- a/runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md +++ b/runatlantis.io/blog/2025/introducing-atlantis-1-0-0.md @@ -3,7 +3,7 @@ title: Introducing Atlantis 1.0.0! lang: en-US --- -# Atlantis User Survey Results +# Atlantis 1.0.0 The core team is excited to announce the release of Atlantis 1.0.0! This release is many years in the making, and we're excited to be bringing Atlantis into this next chapter. @@ -29,4 +29,4 @@ We are roughly guided by the recommendations [here](https://semver.org/), which As mentioned above, right now backwards incompatible changes are included together with "normal" releases. As we get experience separating these, we will develop a more clear understanding of what it means for a change to be backwards incompatible. For now here are a few guidelines: - Changes to server or repo config such that previously specified valid flag and configuration immediately fail -- Changes to behavior like when applies and plans are run, except when gated by a new flag or setting \ No newline at end of file +- Changes to behavior like when applies and plans are run, except when gated by a new flag or setting