Skip to content
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.

Sign up for GitHub

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

Jump to bottom

!!! THIS GEM IS NOT SUPPORTED CURRENTLY (see details inside) !!! #343

Open
styx opened this issue May 6, 2015 · 6 comments
Open

!!! THIS GEM IS NOT SUPPORTED CURRENTLY (see details inside) !!! #343

styx opened this issue May 6, 2015 · 6 comments

Comments

@styx
Copy link

styx commented May 6, 2015

Currently, this repo is abandoned. There is a fork located at https://github.com/state-machines/state_machines which is supported. Also take a look at https://github.com/state-machines/ to see the list of available alternative statemachine realizations. Please don't file bugs here. File them at https://github.com/state-machines/state_machines/issues
@styx styx changed the title THIS GEM IS NOT SUPPORTED CURRENTLY (see details inside) !!! THIS GEM IS NOT SUPPORTED CURRENTLY (see details inside) !!! 💣 May 7, 2015
@styx styx changed the title !!! THIS GEM IS NOT SUPPORTED CURRENTLY (see details inside) !!! 💣 !!! THIS GEM IS NOT SUPPORTED CURRENTLY (see details inside) !!! May 7, 2015
@styx styx mentioned this issue May 8, 2015
Open
@arches arches mentioned this issue Jun 19, 2015
Closed
@rosskevin
Copy link

@styx Please edit your link to https://github.com/state-machines/state_machines

Thank you for the notice, but we are getting traffic and questions in the sub-project for activerecord :)

@styx
Copy link
Author

styx commented Jun 20, 2015

@rosskevin thnx, done.

@kelso
Copy link

kelso commented Jun 30, 2015

Thanks for info and link! I found one failing test while upgrading Rails 4.0 to 4.1. Oh, tests are so important. Quick tip for others: Just change gem 'state_machine' to gem 'state_machines'. Nice 😎

@diaclavijo
Copy link

Maybe someone could write a more clearer message in the Readme that the project has been abandoned?

@styx styx mentioned this issue Feb 17, 2016
Open
@styx
Copy link
Author

styx commented Feb 17, 2016

@diaclavijo good idea, but if that was possible it would be done already.

This was referenced Sep 5, 2016
Open
Closed
@adrianob adrianob mentioned this issue Oct 18, 2016
Merged
@KelseyDH
Copy link

Would be really nice for the maintainer of this repo to redirect people over to the new gem. Ruby toolbox still points here.

jrmhaig added a commit to ministryofjustice/Claim-for-Crown-Court-Defence that referenced this issue Jun 25, 2021
@jrmhaig
Remove state_machine in favour of state_machines
7084622 
The [`state_machine`](https://github.com/pluginaweek/state_machine) gem is
deprecated and was forked in 2015 as [`state_machines`.](https://github.com/state-machines/state_machines)
See: pluginaweek/state_machine#343

As it happens, we already include `state_machines` as a dependency on
`state_machines-activerecord` and `state_machines-audit_trail` so all that
needs to be done is to remove `state_machine` from the `Gemfile`.

As `state_machine` and `state_machines` provide the same functionality, and
there may have been changes to the latter since 2015, there is a possibility
that the ordering of library loading means that we have still been using the
old version and so some testing is required to ensure that there are no breaking
changes.
@jrmhaig jrmhaig mentioned this issue Jun 25, 2021
Closed
This was referenced Mar 3, 2023
Merged
Open
This was referenced Jul 1, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kelso @styx @rosskevin @diaclavijo @KelseyDH