-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.0 #63
Comments
Happy New Year! 🎊 I'm definitely on board with getting to 1.0 soon. I'd love to come to a solution for #23 as well for 1.0, but again, not mission critical, more just a nice to have, but definitely one that'd break our existing API. My big motivation behind this is making Beyond any further discussion around #23 specifically, I'd say I'm all on board for getting 1.0 out the door soon. I think we're getting to a mature enough point with this that I'd feel confident tagging a 1.0 version! |
👍 Waiting for 1.0. |
Chatting with @hyperspacemark a bit offline, starting to gameplan a bit what this release might look like. We decided that adding support for table view clearing to Additionally, we'd like to see Version 2.0 include support for a more generic, protocol-y @hyperspacemark mentioned he'd submit a PR to address #50. After this, we'll tag a v1.0.0 from master! |
1.0 was released! |
I'd love to get a release with #60 but that removes functionality. Should the next version be 1.0? There's a few other breaking changes I'd like to make before we 1.0 (order of initializer params, maybe remove UUID from Row).
Anyway, 1.0 feels like such a big commitment. Are we okay making a breaking change before 1.0 (like CocoaPods :P) and just do 0.3.0 with what's in master and defer the big commitment of 1.0?
What do you think @eliperkins @ayanonagon @hyperspacemark (and anyone else)?
The text was updated successfully, but these errors were encountered: