What should be in Ruby's 2016 Backlog?


#1

Let's say we're all on the Ruby Language project and we're in our backlog planning meeting for 2016. What epics/features/stories should Ruby focus on? Is it time to deal with concurrency? Do we need to focus on making Rails API-only? Are there more language level tweaks that are important? Feel free to include things like Rails, Sinatra, other frameworks in your comments.

What do you think?


#2

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.