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

Release 2.0.0 #144

Closed
rwz opened this Issue Sep 11, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@rwz
Collaborator

rwz commented Sep 11, 2013

things to do:

  • drop ruby 1.8 support
  • implement sane extracting for ?-methods (see #142)
  • remove deprecated code
  • maybe implement dependency tracking for russian-doll caching (see #126)
  • pull #143 (only if rails +1 this)

@ghost ghost assigned rwz Sep 11, 2013

@rwz

This comment has been minimized.

Show comment
Hide comment
@rwz

rwz Sep 11, 2013

Collaborator

@dhh I'd like to hear your feedback on such major changes. Don't want to do something you wouldn't approve in the end

Collaborator

rwz commented Sep 11, 2013

@dhh I'd like to hear your feedback on such major changes. Don't want to do something you wouldn't approve in the end

@rwz

This comment has been minimized.

Show comment
Hide comment
@rwz

rwz Sep 11, 2013

Collaborator

Also, we might want to drop MultiJson dependency and replace it with bundled JSON, since 1.9 has it in stdlib.

That'd speed up things a little for folks who use stdlib or gemified JSON because of the removal of MultiJson wrapping code. On the other hand, it'll slow down generation for people who use custom adapters, like Oj or Yajl.

Not sure about this one.

Collaborator

rwz commented Sep 11, 2013

Also, we might want to drop MultiJson dependency and replace it with bundled JSON, since 1.9 has it in stdlib.

That'd speed up things a little for folks who use stdlib or gemified JSON because of the removal of MultiJson wrapping code. On the other hand, it'll slow down generation for people who use custom adapters, like Oj or Yajl.

Not sure about this one.

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Sep 11, 2013

Member

I've replied on all the individual tickets. I'm ok with the other parts not mentioned on the tickets. But let's wait with a 2.0 release until Rails 4.1 drops. I think that's going to be around december or so, if all goes according to plan (ha!).

Member

dhh commented Sep 11, 2013

I've replied on all the individual tickets. I'm ok with the other parts not mentioned on the tickets. But let's wait with a 2.0 release until Rails 4.1 drops. I think that's going to be around december or so, if all goes according to plan (ha!).

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