v1.0.0 alpha release#219
Conversation
|
Should we deal with all design pattern issues and pull requests before a probable 1.0 release? After 1.0, they would be no longer changed. May discuss on each of them and close or accept all possible designs. |
|
Ideally yep, see #177 for the list, mostly predicated on coming to a consensus as to #172 (and #98) as you mentioned in the chat. However, I don't think this necessarily needs to block an alpha release, and there's a balance to be struct somewhere between avoiding breaking releases while not blocking e-h improvements indefinitely :-/ |
|
Ohh yes, do not need to block alpha here. Just block before the final 1.0.0 :) |
|
I think that the only thing that should block v1.0.0 is rust-embedded/wg#435. We can add all the other changes after this release. Also I don't understand why we need |
|
Yes, I agree. There should be no more blocks here |
The idea is to shake out some kinks before doing the final release. Hopefully there're no breaking changing but at the moment it's hard to say since its non-trivial to test with the required level of scrutiny without having a crate on crates.io since you get all kinds of versioning funnyness when using traits from an unreleased crate in other crates. I could even see folks follow suit by releasing alpha versions of adapted crates so we could properly level up the whole ecosystem at once. |
therealprof
left a comment
There was a problem hiding this comment.
Need to figure out what to do about CHANGELOG.md
Signed-off-by: Daniel Egger <daniel@eggers-club.de>
|
turns out i can't approve this because it's my pr, but, lgtm~! |
|
bors r+ |
🎉🎊🥳
See #177 for progress on blocking issues