-
-
Replying to @derekprior
@derekprior@sgrif unless someone explicitly declares what 1.0 means in a project I find it a pretty meh measure of stability.1 reply 0 retweets 0 likes -
Replying to @derekprior
@schneems@sgrif This is an often disregarded bit of SemVer (particularly in Ruby) and we all do just fine. Semantics, but that’s the point.1 reply 0 retweets 0 likes -
Replying to @derekprior
@derekprior@sgrif didn't realize that 1.0 behavior was actually called out in the spec, thanks.1 reply 0 retweets 0 likes -
Replying to @schneems
@schneems@derekprior@sgrif yeah, npm is too pushy about that IMO. `npm init` defaults new projects to 1.0.0. A littttle presumptuous.1 reply 0 retweets 2 likes -
Replying to @searls
@searls@schneems@derekprior@sgrif yea how dare the first version of something be 1. :)1 reply 0 retweets 1 like -
Replying to @bphogan
@bphogan@schneems@derekprior@sgrif the implication in semver is "this thing you just generated is promised as stable the moment you push"2 replies 0 retweets 0 likes -
Replying to @searls
@searls@schneems@derekprior@sgrif …. so maybe don’t push till it’s stable? :)2 replies 1 retweet 0 likes -
Replying to @bphogan
@bphogan@searls@derekprior@sgrif stable is relative. 2.0 could be a totally different api2 replies 0 retweets 0 likes
@schneems @bphogan @searls @derekprior This is the lacking bit. Bumping major should not be a license to change everything. There is a cost
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.