4 ms·
It is in v0, breaking changes are expected. If the new version is not compatible, wait until it is and then upgrade. It is also completely reasonable to not wan
by dj_mc_merlin 6y ago
It is in v0, breaking changes are expected. If the new version is not compatible, wait until it is and then upgrade. It is also completely reasonable to not want to use it until it is stable.
- HatchedLake721 6y agov0 or not doesn't matter, Terraform doesn't follow semantic versioning.
- kubanczyk 6y agoOf course it does follow semantic versioning, so far. > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable. https://semver.org/#spec-item-4 https://semver.org/#spec-item-4 > At HashiCorp we take the idea of a v1.0 very seriously. https://github.com/hashicorp/terraform/issues/15839#issuecomment-323106524 https://github.com/hashicorp/terraform/issues/15839#issuecom... > Terraform 0.14 release. That's our last chance to deprecate features or introduce breaking changes, before 1.0. Will we have 0.15? That's anyone's guess at this point. I honestly don't know. https://www.hashicorp.com/resources/the-path-to-terraform-1-0 https://www.hashicorp.com/resources/the-path-to-terraform-1-...
- HatchedLake721 6y agoCalling a software that's been out for 6+ years powering everyone's IaaC from startups to multi-billion companies around the world as "initial development" to fit into SemVer is a stretch for me.
- cies 6y agoKeeping a software in "0.x" land while being used in production so much is a bit disingenuous, dont you think? I mean: it's up to Hashicorp how to version their software, but this is simply messing with expectations in my book.