-
Notifications
You must be signed in to change notification settings - Fork 124
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
Cut a new release #166
Comments
At the moment only @FFY00 can do this 🤷 But we could do release |
I would really like #132 to be fixed before a new release, which is not that straight forward because of the tests. But since there are major issues with the current one, I think we can defer it. |
Presumably we should make the version Also, I think that at this stage in the project there's no reason to delay releases waiting on new features or bugfixes, as long as the version on master is an improvement on the released version. |
I am fine with that. |
Agreed with @pganssle, we should release as often as possible until we reach 1.0. |
Just released 0.1.0 😊 |
In #158, I encountered an issue that's been fixed in master. It would be nice to have a release that includes that fix.
The text was updated successfully, but these errors were encountered: