Just realized that ton of @rustlang crates are treating `0.x.y` versions exactly the same as you would treat `x.y.z` versions.
-
Show this thread
-
Maybe we should release 1.0.0 earlier, and not be as allergic to 1+n major versions?
1 reply 0 retweets 1 likeShow this thread -
Replying to @udoprog
This is how most ecosystems use x==0, so so do we. Moving to 1.0 earlier is certainly a regular topic of debate though!
1 reply 0 retweets 0 likes -
Replying to @rustlang
If x==0 no longer means "Anything may change at any time", what does it mean? The project is not "done"?
1 reply 0 retweets 0 likes -
Replying to @udoprog
It means “we’re not committing to a stable API for a long time”
1 reply 0 retweets 0 likes -
Replying to @rustlang
Possibly. What initially prompted my comments were projects that have been stable in their 0.y state for a long time. Maybe I should encourage them to move to a major version scheme instead :)
1 reply 0 retweets 1 like
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.
