It is extremely irresponsible to make a breaking change without bumping a major version
krainboltgreene opened this issue · 4 comments
krainboltgreene commented
It is extremely irresponsible to make a breaking change without bumping a major version
wuputah commented
Not rude:
"Thanks for shipping!"
"You're welcome."
Rude:
This issue.
krainboltgreene commented
Rude: Shipping code that will break things without notifying the users in
an agreed upon standard.
…On Mon, Jun 25, 2018 at 10:42 AM JD ***@***.***> wrote:
Not rude:
"Thanks for shipping!"
"You're welcome."
Rude:
This issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUb2c-TIWiT2NvwdnC0MdKJENuy-tndks5uASEEgaJpZM4U2den>
.
--
Kurtis Rainbolt-Greene, Software Developer
Founder of Difference Engineers
2985 San Marino St.
Los Angeles, CA 90006
202-643-2263
wuputah commented
krainboltgreene commented
Since I've worked on that document, I'll help you out with that link:
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.