Skip to content

Roadmap for 2.0.0 #3990

Description

@kddnewton

Opening this issue just for public visibility into the stuff I'm pushing on/expecting to happen before 2.0.0, which should hopefully be in the near-ish future. Now that all of the various bugs that I know about related to the actual structure of the tree have been fixed (https://bugs.ruby-lang.org/projects/ruby-master/issues?query_id=380), I'm looking to get the following stuff over the line before the next major.

Stuff on this repository in particular:

Other stuff in the ecosystem I would like stabilized:

Other gems that could use migrating that would be nice but not required (ordered by downloads):

Activity

  1. amy-hashi commented on May 28, 2026

    @amy-hashi

    Will there be another release in the 1.x series before 2.0? We are having to build from source in order to get the latest fixes, since it's been so long since a release was cut. (Thank y'all for all the attention to open issues and PRs!)

  2. kddnewton commented on May 28, 2026

    @kddnewton
    CollaboratorAuthor

    Will there be another release in the 1.x series before 2.0? We are having to build from source in order to get the latest fixes, since it's been so long since a release was cut. (Thank y'all for all the attention to open issues and PRs!)

    I wasn't planning on it. Is there a particular fix you're looking for? I can make a patch release and just backport a particular thing if you need. But main has a bunch of breaking changes so we can't cleanly release that atm.

  3. eregon commented on May 30, 2026

    @eregon
    Member

    Do you have some examples of the breaking changes, do they affect only the C API, Ruby API, something else?

    FWIW in TruffleRuby I'm currently using 5172b2a because I want some of the newer fixes (e.g. Ripper-related) and I feel asking for a release every time I update (e.g. Jan 28, Mar 26, Apr 6, May 14) would be a non-trivial overhead so I'm picking commits from master.

  4. amy-hashi commented on Jun 2, 2026

    @amy-hashi

    Yes, it was this bug in particular -> #4118

  5. kddnewton commented on Jul 20, 2026

    @kddnewton
    CollaboratorAuthor

    Closing as the remaining tickets are open and we don't need this tracking anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions