-
-
Notifications
You must be signed in to change notification settings - Fork 273
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 1.0 #358
Comments
I've been using celluloid-io, and celluloid, for a bit now on my favorite personal project and I am totally ready to see this 1.0 (and beyond). It's amazing work! |
👍! |
How about celluloid maybe use semantic versioning so that bundler and rubygems don't go bananas? |
We certainly plan on using semantic versioning after 1.0 |
With a lot having changed lately, and some soulsearching having happened regarding some refactoring projects needing done, here's a tentative schedule suggestion to get us up to https://groups.google.com/d/msg/celluloid-ruby/xUFSTGX1sKY/OoQI-jivoAIJ |
Closing as stale. If you are still interested in this issue, please reopen it. |
@tarcieri, if we can get together a succinct list of what's included in this milestone, some of us can iterate on this over the Spring until it's finally done. Or did something specific prompt reopening? |
I did a sweep of the open issues and closed this one accidentally |
All has been quiet in Gitter and here since January - has the second wind died down? Are downloads still crazy high? Is there hope of this being revived? |
#789 is the place to start, unfortunately of all of the prospective interested people who said they'd triage that release, no one has seen it through so far |
I've been looking at the angle of reworking the actor system by implementing a |
I think the main thing Celluloid could benefit from, provided anyone wants to keep it going, is another release (#789), followed by several other releases of minor changes and bugfixes. Where things started to wrong before was with changes that were too invasive, creating too many bugs. |
Especially since I introduced most of those changes, I can start to budget a couple hours a week to |
We should release 1.0! While there's an awful lot of stuff we could potentially fix before shipping a "1.0" release, I think the biggest thing we can do is ship the
Actor
/Cell
split as 0.16 (#357) and work to fix everything that breaks as a result 😉What about the rest of the stuff? Well, that's what 2.0 is for!
The text was updated successfully, but these errors were encountered: