Release memchaser 0.5.2 with Addon SDK 1.13.2 #162

Closed
whimboo opened this Issue Feb 19, 2013 · 6 comments

Comments

Projects
None yet
2 participants
Contributor

whimboo commented Feb 19, 2013

There was a major leak in the SDK which has been fixed with 1.13.2. We should update the internally used version of the SDK and get memchaser 0.5.2 released.

See:
https://blog.mozilla.org/addons/2013/02/12/announcing-add-on-sdk-1-13-2/

whimboo was assigned Feb 19, 2013

Contributor

whimboo commented Feb 19, 2013

Looks like we can't simply bump the SDK to 1.13.*. After doing that memchaser doesn't initialize anymore because memory.js is not defined. Something is going wrong in there. I might have to take a look at later this week.

Contributor

whimboo commented Feb 19, 2013

Something broke us between 1.11 and 1.12.

Contributor

whimboo commented Feb 19, 2013

Those are the new layout changes which went into 1.12:
https://wiki.mozilla.org/Labs/Jetpack/Release_Notes/1.12

Member

KWierso commented Feb 19, 2013

So, #163 has the changes required for 1.13.2's... require... statements, and now includes the update to 1.13.2 that actually requires those changes. :)

Travis doesn't seem to be complaining with all of those changes, though I don't know if that means everything's working.

Contributor

whimboo commented Feb 19, 2013

As mentioned on #163 we will do the minimal approach for now and only update the require line for local modules. That will keep backward compatibility with older versions of the SDK.

@whimboo whimboo added a commit to whimboo/memchaser that referenced this issue Feb 19, 2013

@whimboo whimboo Release memchaser 0.5.2 with Addon SDK 1.13.2 (#162) 8753a83
Contributor

whimboo commented Feb 19, 2013

It's released!

whimboo closed this Feb 19, 2013

whimboo was unassigned by moz-hwine Aug 14, 2015

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