-
Notifications
You must be signed in to change notification settings - Fork 155
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
Release 0.1 #38
Comments
Yeah, it's not released because it's still kinda broken. Particularly, #30 is a concern. |
If there is no regression, I prefer releasing and fixing #30 in next version. |
Fair enough. I'm going to review all open issues etc this week. I also wanna change some of the word in the new logging system before making it final. |
We're going to do a release without #30. Reopening. |
👍 |
At this point #37 is the only real real blocker to getting a "final" beta out. The rest is documentation and can go out in GA without a beta. |
Speaking of documentation, the README needs be much updated. The good news is that the source is now ridden with comments. |
0.1.0beta4 is out. (commit: 611816f) It hasn't undergone a ton of testing, but it passes the tests that have been contributed so far. (see |
What I mean is: Please test it with your apps and report back! Many thanks. |
it's out. |
Hi guys, any reason to not release 0.1.0? Just curious if there was an ongoing discussion I didn't see. I've been using
tag: 'v0.1.0beta3'
in production for a few months...The text was updated successfully, but these errors were encountered: