docs: Atlantis 1.0.0 blog post #5296
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nitrocode
reviewed
Feb 5, 2025
X-Guardian
reviewed
Feb 16, 2025
Comment on lines
+22
to
+32
| ### 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. | ||
|
|
||
| ### 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 |
There was a problem hiding this comment.
Once v1.0.0 is released, any breaking changes to the Atlantis server configuration parameters, server-side repo config or API should trigger a major version bump.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
Blog post for Atlantis 1.0.0
why
Introduce 1.0.0, explain why, etc.
tests
N/A
references