Update dependencies

[ahumphreys87]

We'd need to update radio, metal, and babysitter, but this is just a start to check out the failing tests and begin the conversation of what it might look like to have the latest dependencies for the v3 launch.

would resolve #2446

Opening in favour of #2555

[paulfalgout]

So these failing tests must be fixed here jashkenas/backbone#3613 correct?

[ahumphreys87]

I believe that is the real fix - however we can make our tests bypass this
code in backbone by enabling pushState on the router - do we wanna do that
in our tests? Would allow us to get this released - pretty confident it's
jsDom specific

On Monday, 18 May 2015, Paul Falgout notifications@github.com wrote:

So these failing tests must be fixed here jashkenas/backbone#3613
jashkenas/backbone#3613 correct?

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

[paulfalgout]

I'll feel better when 1.2.1 comes out fixing:
jashkenas/backbone#3603
jashkenas/backbone#3615

But I don't know that it is worth waiting on either..

[paulfalgout]

I think maybe we should go with 1.0.0 - ~1.2 for backbone. perhaps even 1.4.4 - ~1.8 for underscore.

There will likely be some 1.2 patch fixes in the near future. But there's more discussion about a Bb 2.0 than a 1.3, so rather than have to manage dependencies for the next few month, I'd bet it'd be safe to go this ~ route.

For that matter even ~1 for Bb

[ahumphreys87]

If we do that we are relying on BB not releasing anything breaking in a minor or patch. Should we risk that?

[paulfalgout]

And there we have it. Bb 1.2.1 released.

Time to update all the dependencies

[ahumphreys87]

Awesome I'll update the deps. How do you feel about us updating wreqr to
support latest BB in 2.x @paulfalgout? I think we should tbh - 3.0 looks a
while away still and we don't want to block people

On Friday, 5 June 2015, Paul Falgout notifications@github.com wrote:

And there we have it. Bb 1.2.1 released.

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

[paulfalgout]

agreed. those who can't upgrade to v3 quickly may still want to upgrade to Bb 1.2.1 and I don't see any reason to prevent that.

[ahumphreys87]

bumped backbone to 1.2.1 and rebased.

Once this is in ill cherry-pick onto 2.4.2

[paulfalgout]

This is great once:

• update backbone dep backbone.wreqr#67
• bump backbone dep backbone.babysitter#60
• update Backbone dep backbone.radio#225

And for next we'll really need to update metal.

[ahumphreys87]

I checked metal and it seemed ok. Not specific like ours though.

On Monday, 8 June 2015, Paul Falgout notifications@github.com wrote:

This is great once:

• update backbone dep backbone.wreqr#67
  update backbone dep backbone.wreqr#67
• bump backbone dep backbone.babysitter#60
  bump backbone dep backbone.babysitter#60
• update Backbone dep backbone.radio#225
  update Backbone dep backbone.radio#225

And for next we'll really need to update metal.

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

[ianmstew]

Agree this is much needed in 2.4.2. With all tests passing I don't see any reason not to merge. 👍