Skip to content

Commit

Permalink
No need to shout.
Browse files Browse the repository at this point in the history
  • Loading branch information
nedtwigg committed Jan 11, 2020
1 parent 9064092 commit 9f42cfb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ We also support other version schemas, like `2.0` instead of `2.0.0`, or `brand.

You might not think that your library is ready yet. But once someone has decided to use your library as a dependency, who cares how good *you* think it is. *Your users* think that it's good! Or at least *good enough*. The terrible thing about `0.x` is that *the more unstable a codebase is, the more valuable **(concise compatibility guarantee).(new feature advertisement).(lowest downside risk to upgrade)** would be!*

But habits are what they are, and you're going to keep publishing things with `0.x`. I will judge you for that, but Spotless Changelog won't. It will just increment the `ADDED` version (`0.1.0`, `0.2.0`, `0.3.0`, etc) whether your changelog has `**BREAKING**` or just `### Added`. See how the information is getting lost?
But habits are what they are, and you're going to keep publishing things with `0.x`. I will judge you for that, but Spotless Changelog won't. It will just increment the `added` version (`0.1.0`, `0.2.0`, `0.3.0`, etc) whether your changelog has `**BREAKING**` or just `### Added`. See how the information is getting lost?

### Alphas, betas, release-candidates, etc.

Expand Down

0 comments on commit 9f42cfb

Please sign in to comment.