-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
New release with changes? #39
Comments
definitely not 1.0. The changes are all WIP, have a close watch on #18 to see the progress there. @theangryangel does the main work in that Issue, and I ATM have a 70+ hours week in my day job (as MD). But anyway, the low-level API is pretty stable and won't change much any more. |
What about a 0.0.6 release? A new pypi release would trigger some notification on our side (and would probably mean we try the new version with our current code). Releasing regularly means that we don't have to do too much catch-up at once (and we could provide input if a new release breaks our use case). |
Yes, 0.0.6 is definitely the way to go, good idea. I'll do that. Is that OK for all to close this issue after that? |
Sure, 0.0.6 makes sense to me |
Ok, new version 0.0.6 is available on pypi, please test as you wish ;-) |
Thank you. I just noticed that we used a pre-release version from August or so already as we need some of the changes :-) |
It seems that a lot of changes have been introduced in pydifact since the last release on pypi. Are there plans for a new 1.0 release any time soon?
The text was updated successfully, but these errors were encountered: