search

adamreeve / semver.net

Semantic versioning for .NET
MIT License
117 stars 22 forks source link

1.0 release #33

Closed felixfbecker closed 6 years ago

felixfbecker commented 6 years ago

A semver package should follow semver :)

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

http://semver.org/#how-do-i-know-when-to-release-100

adamreeve commented 6 years ago

:+1: you're right of course, 1.0 gives a sense of something finished, but people are depending on the API so it should definitely be 1.0 by now. I'll create a new 1.0 release and make sure I follow semver for future releases :)

adamreeve commented 6 years ago

I've released 1.0.0 to NuGet now :)