Prepare release for v5.0.0

[tute]

There are two backward incompatible changes.

cc @jyurek @iwz

[maclover7]

Should we hold off on releasing this until Rails 5 lands, I think we are planning on dropping support for 3.2 as apart of that release?

[iwz]

There was a fix for Rails 3.2 I'd like to get into a release. Maybe we can
cut from there?

On Sat, Sep 5, 2015, 9:24 PM Jon Moss [email protected] wrote:

Should we hold off on releasing this until Rails 5 lands, I think we are
planning on dropping support for 3.2 as apart of that release?

—
Reply to this email directly or view it on GitHub
#1991 (comment)
.

[tute]

There was a fix for Rails 3.2 I'd like to get into a release. Maybe we can cut from there?

Sounds good. master got so many changes, including two backward incompatible ones. We could do a patch release with your commit. What is its SHA?

[tute]

I think we are planning on dropping support for 3.2 as apart of that release?

Yes.

Should we hold off on releasing this until Rails 5 lands

We could hold off the backwards incompatible changes, but a minor version with everything else would be healthy I think. Let's ask @jyurek!

[jyurek]

I think a minor version without the backwards incompatible changes are probably best right now, and we can discuss things like the MD5->SHA change.

[iwz]

@tute the SHA I'm looking for is c740fb1

[tute]

After we release #1995, I'll merge master into it, and rebase this branch when we decide it's time to do the major release. Thank you for your input.

[detournemint]

It seems like #1995 was merged in, what's the status on this?

[tute]

We'll release the major version after Rails 5 is out. The commit that fixed a Rails 3.2 regression is already out.