You're not mature enough to release your first version as v1 (12 mins read).
Why you should never release your first iteration of a project as your v1.0.0, but it should instead by v0.1.0.
by 
Jamie Tanna
.
#versioning.
Tag versioning
Bookmarked
Breaking changes: a tooling problem - Richard Marmorstein
Post details
How could our tools change to reduce the cost of breaking changes?
by Jamie Tanna
.
#versioning.
Bookmarked
Versioning as Communication
Post details
Talking through why choosing a versioning scheme is of vital importance and why SemVer is the best option for most.
by Jamie Tanna
.
#versioning.
Liked
To infinity and beyond: enabling the future of GitHub's REST API with API versioning | The GitHub Blog
by
Post details
We’re introducing calendar-based versioning for our REST API, so we can keep evolving our API, whilst still giving integrators a smooth migration path and plenty of time to update their integrations.
by Jamie Tanna
.
#github
#versioning.
I've been bitten by pinning to latest versions before and definitely agree that where possible we should make sure that things are pinned exactly.
Then we can use tools like Whitesource Renovate / Dependabot to manage updates automatically.
Bookmarked
Never update anything | blog.kronis.dev
Post details
My blog, where i attempt to collect my thoughts and share the occasional interesting topic with others
by Jamie Tanna
.
#versioning
#version-pinning
#package-management.
Liked
a post on Twitter
Post details
https://twitter.com/bagder/status/1429082502619189252
a fun detail is that just about all programs written against that libcurl release can still be used unmodified with the latest libcurl release...
Daniel 🥌 Stenberg (@bagder)Sat, 21 Aug 2021 14:40 +0000
by Jamie Tanna
.
#versioning.
Liked
a post on Twitter
Post details
Best explanation of SemVer I've seen yet: FAILS.FEATURES.BUGS
Post details
https://twitter.com/simonw/status/1423677380694986761
Absolutely. The thing about semver major version numbers are that they don't mean new stuff, they're a permanent reminder of how many times you got the API wrong. Semver doesn't mean MAJOR.MINOR.PATCH, it means FAILS.FEATURES.BUGSWill McGugan (@willmcgugan)Fri, 06 Aug 2021 16:13 +0000
Simon Willison (@simonw)Fri, 06 Aug 2021 16:21 +0000
by Jamie Tanna
.
#semver
#versioning.
Liked
a post on Twitter
Post details
https://twitter.com/simonw/status/1423677380694986761
Absolutely. The thing about semver major version numbers are that they don't mean new stuff, they're a permanent reminder of how many times you got the API wrong. Semver doesn't mean MAJOR.MINOR.PATCH, it means FAILS.FEATURES.BUGSWill McGugan (@willmcgugan)Fri, 06 Aug 2021 16:13 +0000
by Jamie Tanna
.
#semver
#versioning.
Why I Consistently Reach for Server-Driven Content Negotiation (For Versioning) (5 mins read).
Why I use server-driven content negotiation for APIs to allow for versioning and allowing different representations of APIs.
by Jamie Tanna
.
#api
#content-negotiation
#rest
#web
#versioning
#version-pinning.
You're currently viewing page 1 of 1, of 28 posts.