Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upBreaking changes #32
Comments
This comment has been minimized.
This comment has been minimized.
|
Is https://killercup.github.io/bitrust/log.json the correct place to get a machine-readable format? How frequently do you update, or is it automated? Out of curiosity, how does bitrust decide what a breaking change is? |
This comment has been minimized.
This comment has been minimized.
|
Believe it or not, I currently have a tmux pane open somewhere where I from time to time type Up, Enter to update this… If you have the rust-lang/rust repo cloned, and are using Rust in your backend anyway: It might be easier to just take the tiny bit of code from https://github.com/killercup/bitrust/blob/rust/src/main.rs I would be very happy to have this integrated somewhere more official than my random Github page! |
anp
added a commit
that referenced
this issue
Jun 7, 2016
This comment has been minimized.
This comment has been minimized.
|
Adding a useful links page with this included for now, will investigate further integration in a little bit. |
This comment has been minimized.
This comment has been minimized.
|
Boilerplate: I'm going to refocus this project on rfcbot, since that's the primary usage rusty-dash.com is seeing. |
killercup commentedJun 2, 2016
Might be interesting to see how often breaking changes happen, though they are limited to unstable/internal stuff now.
While a metric would be cool ("It's been 11 days since the last
work accidentbreaking change"), feel free to link to http://killercup.github.io/bitrust/ in the meantime :)