-
-
Notifications
You must be signed in to change notification settings - Fork 77
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 #58
Comments
We can take a final pass through all the public methods we expose. If all of them are described by external interfaces, I think we have now gotten to a fully stable public API. Since we aren’t planning to add random methods of our own invention here, any bugs can still be fixed under version 1.0.0 but it does communicate that the API is done. Should #49 set the upcoming “unreleased” to 1.0.0 to make this a promise? |
That is my intention but I want to "play it safe" and do 0.4.0 first. |
Hm.. With a second thought... |
Hmm, I have no ideas what files I have and have not been involved with now. Should I try to find out to add |
I fixed that in #69 |
Are we ready for tagging 1.0? |
I opened #71 because I noticed that when reviewing a PR… but otherwise I think we are set! |
Should I tag the release now? |
Do whatever you want with #72 and then go for it 👍 Anything else will simply be future work. I think these last 2 days have done enough streamlining! |
#72 is just meta. That could be handled later. |
Wohoo |
I suggest version 0.4.0 should be the last release before 1.0.
Anything else we need to add or remove?
The text was updated successfully, but these errors were encountered: