Skip to content

Flip → Flipflop? #51

Description

@pda

Flip has not been actively maintained. @rolftimmermans created a backwards-incompatible fork called Flipflop which looks in far better shape. Should Flipflop completely replace Flip? I can see a few ways forward:

  1. Merge Flipflop into Flip, tag it as v2.0.0, release the v2 gem, give @rolftimmermans / @voormedia full access to flip on GitHub and RubyGems. That doesn't rule out maintaining a v1 branch for backwards-compatible fixes. It would make sense in this option to shut down https://github.com/voormedia/flipflop pointing people to flip.
  2. Officially halt development on Flip, close all issues and PRs, modify the README to endorse migration to Flipflop.
  3. Bring some collaborators in to continue development on Flip, keep it separate from Flipflop. I think this only makes sense if it's to keep flip reasonably backwards-compatible compared to the breaking changes and trickier migration to Flipflop (assuming that's true?).
  4. ¯_(ツ)_/¯

In all cases, existing commits, tags and gem releases of flip would continue to work.

/cc @rolftimmermans @kwent @jcoyne @olleolleolle @jippeholwerda as recent contributors (sorry if I responded late or never to your PRs!)

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions