Skip to content

v3.0.0 #234

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

Merged
merged 1 commit into from
Apr 15, 2016
Merged

v3.0.0 #234

merged 1 commit into from
Apr 15, 2016

Conversation

dgalarza
Copy link
Contributor

No description provided.

@tute
Copy link

tute commented Apr 15, 2016

This looks great. Do we need upgrade instructions?

@mike-burns
Copy link
Contributor

  1. Yay! LGTM.
  2. Why 3.0.0 instead of 2.5.0?

@tute
Copy link

tute commented Apr 15, 2016

Why 3.0.0 instead of 2.5.0?

Is #221 backwards incompatible?

@mike-burns
Copy link
Contributor

Aha, it probably is. 3.0.0 it is!

@dgalarza
Copy link
Contributor Author

dgalarza commented Apr 15, 2016

Is #221 backwards incompatible?

Correct!

@dgalarza
Copy link
Contributor Author

This looks great. Do we need upgrade instructions?

I don't think we do. The README was previously updated on the removal of caching with instructions on how to move forward if needed. I think that will suffice.

Thanks @tute / @mike-burns

@dgalarza dgalarza merged commit cbab60f into master Apr 15, 2016
@teoljungberg teoljungberg deleted the dg-v3 branch April 28, 2016 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants