Skip to content

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

Merged
merged 2 commits into from
Jul 9, 2015
Merged

Conversation

pitr-ch
Copy link
Member

@pitr-ch pitr-ch commented Jul 8, 2015

please see commit messages

@pitr-ch pitr-ch added the enhancement Adding features, adding tests, improving documentation. label Jul 8, 2015
@pitr-ch pitr-ch self-assigned this Jul 8, 2015
@pitr-ch pitr-ch added this to the 1.0.0 Release milestone Jul 8, 2015
@jdantonio
Copy link
Member

@pitr-ch Is this ready to merge, or is it waiting until after I release 0.9.0?

@sschepens
Copy link
Contributor

@jdantonio @pitr-ch I would love this to be in a release, I have tested locally and seems to work.
Anyway, this affects only concurrent-edge so could be release separately from 0.9.0

@pitr-ch
Copy link
Member Author

pitr-ch commented Jul 9, 2015

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.

@pitr-ch pitr-ch modified the milestones: 0.9.0 Release, 1.0.0 Release Jul 9, 2015
@pitr-ch
Copy link
Member Author

pitr-ch commented Jul 9, 2015

cc @iNecas

@iNecas
Copy link
Contributor

iNecas commented Jul 9, 2015

Will check in an hour

@iNecas
Copy link
Contributor

iNecas commented Jul 9, 2015

works for me

pitr-ch pushed a commit that referenced this pull request Jul 9, 2015
Future, Actor improvements
@pitr-ch pitr-ch merged commit d31bf98 into ruby-concurrency:master Jul 9, 2015
@jdantonio
Copy link
Member

@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!

@pitr-ch
Copy link
Member Author

pitr-ch commented Jul 9, 2015

@jdantonio completely agree, I meant a next release after the first one companioning 0.9 core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding features, adding tests, improving documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants