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.

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

Upgrading path #1694

Open
beauby opened this issue Apr 20, 2016 · 7 comments
Open

Upgrading path #1694

beauby opened this issue Apr 20, 2016 · 7 comments

Comments

@beauby
Copy link
Contributor

beauby commented Apr 20, 2016

Just a reminder that we have to write a clear note on how to upgrade from 0.8/0.9, with new features, changed behaviors, and removed features.
ref: #1005, #1683

@oyeanuj
Copy link

oyeanuj commented Dec 21, 2016

@beauby Are there any upgrading docs for moving from 0.9 to 0.10? I looked through the docs but couldn't find a link - apologies in advance, if I missed something.

@beauby
Copy link
Contributor Author

beauby commented Dec 22, 2016

@oyeanuj Not that I know of, no :/

@oyeanuj
Copy link

oyeanuj commented Dec 22, 2016

@beauby :( Do you know if it is on the radar or a priority?

As someone who is on 0.9, I feel a little stuck - can't upgrade to Rails 5 because 0.9 has some issues with it (#1923) and hard to go from 0.9 -> 0.10 (to use Rails 5) as there isn't feature parity(#1845) and lack of documentation, which means more unknowns of what might or might not work.

Hopefully, it doesn't come off as a complaint or an entitlement, but as a perspective of someone who is excited about upgrading but is encountering issues. I know you guys are doing the best you can!

@beauby
Copy link
Contributor Author

beauby commented Dec 22, 2016

@oyeanuj I'm afraid it will have to come from the community as:

  • AFAIK, no current maintainer has much experience with 0.9 (or 0.8 for that matter), and
  • focus (at least on my side), is mainly on jsonapi support (though I'm currently focused on jsonapi-rb more than AMS).

Listing all the issues/missing features you are encountering would be a great start though.

Hopefully, it doesn't come off as a complaint or an entitlement, but as a perspective of someone who is excited about upgrading but is encountering issues. I know you guys are doing the best you can!

Not at all! (:

@leonelgalan
Copy link
Contributor

@oyeanuj I did the update recently, haven't had the time to compile a list of rules that classify all the changes, but I have a single commit (private repo) that did it and I should be able to go back and start listing each change. I don't have much time now, but I will be happy to chat and help you through the process, just so we can produce a guide for the community. My email is publicly available at my Github page, feel free to contact me through there so we can coordinate the effort better.

@toobulkeh
Copy link

@leonelgalan @oyeanuj -- I'm running into similar issues (stuck on 0.9). Would love some insight into the overall changes!

@oyeanuj
Copy link

oyeanuj commented Apr 18, 2017

@toobulkeh Sorry, I haven't been able to. Ran into some issues and was fairly overwhelming. Personally, I think I'll focus on #1923 and not upgrade. And if that fails, then try this one again!

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

No branches or pull requests

4 participants