-
Notifications
You must be signed in to change notification settings - Fork 419
Future, Actor improvements #363
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
Conversation
@pitr-ch Is this ready to merge, or is it waiting until after I release 0.9.0? |
@jdantonio @pitr-ch I would love this to be in a release, I have tested locally and seems to work. |
As @sschepens said, I've planned it for separate edge release, but we could get it in 0.9. I'll just update documentation and merge today. |
cc @iNecas |
Will check in an hour |
works for me |
@pitr-ch Since the 0.9.0 release will move several classes out of core and into edge, I think we need a full release of edge at the same time. Once we have a 0.1.0 release of edge I think we can release it separately. But I don't think we should release core 0.9.0 while edge is still in pre-release. Thank you for jumping on this! |
@jdantonio completely agree, I meant a next release after the first one companioning 0.9 core. |
please see commit messages