ZeroVer: 0-Based Versioning

• semver

  720 7,020 2.3

  Semantic Versioning Specification

  

That's regular Semantic Versioning

https://semver.org/

> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

> Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.

> If your software is being used in production, it should probably already be 1.0.0.

• terraform

  500 41,118 9.9 Go

  Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.

  

But hey… even terraform made it to v1.0.0 after some time… https://github.com/hashicorp/terraform/releases/tag/v1.0.0

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• neovim

  1,384 76,465 10.0 Vim Script

  Vim-fork focused on extensibility and usability

  

Neovim is listed as a "notable ZeroVer project" and yet it has a 1.0(!!) milestone in the GitHub project page.

https://github.com/neovim/neovim/milestones

• helmfile

  39 4,023 0.0 Go

  Deploy Kubernetes Helm Charts

Helmfile might be a good addition to the list: https://github.com/roboll/helmfile

• Fail2Ban

  49 10,423 8.8 Python

  Daemon to ban hosts that cause multiple authentication errors

  

• terraform-provider-azuread

  12 406 9.2 Go

  Terraform provider for Azure Active Directory

  

We have an internal provider that handles generation of IAM Roles and IAM users via an external API for various security reasons I may or may not agree with. The constant provider changes in 0.10 and upward were extremely painful. We actually ended up having several teams who so hopelessly fubared their tfstates trying to skip minor releases, we ended up having to take it away and put together a task force to do it ourselves across almost 200 repositories.

I’m not sure what you mean by “all three major cloud providers rewrote their own APIs.” Azure[1][2], AWS[3], and Google[4] are all maintained by Hashicorp. In fact, if you peruse the issues you’ll often see PRs opened by employees of the respective providers trying to fix blocking issues and they often devolve into literal begging for Hashicorp to respond and at least tell them why something hasn’t been merged. I know one blocker[5] actually cost Azure a very substantial customer as it languished in Hashicorp’s queue.

Hashicorp’s constant refrain of “Well it’s a 0 version software” while selling enterprise support and constantly shilling their wares as production ready across the entire DevOps space was dishonest.

I appreciate the position they were in and I appreciate even more their attempt to at least put out a good PR move with their 1.0 release. We will see how well it holds up over the years.

Also I pretty clearly said there isn’t much options. What you call “that good” I call “better than everything else but still byzantine and hellish to deal with every time someone DMs me, ‘hey, you know terraform right?’”

1: https://github.com/hashicorp/terraform-provider-azuread

• terraform-provider-azurerm

  83 4,403 10.0 Go

  Terraform provider for Azure Resource Manager

  

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• terraform-provider-aws

  100 9,453 10.0 Go

  The AWS Provider enables Terraform to manage AWS resources.

  

• terraform-provider-google

  16 2,220 9.9 Go

  Terraform Provider for Google Cloud Platform

  

Suggest a related project