Update SDK data for SDK release 1.11

VERIFIED FIXED in 2012-11-01

Status

VERIFIED FIXED
6 years ago
3 years ago

People

(Reporter: canuckistani, Assigned: KWierso)

Tracking

unspecified
2012-11-01
x86
Mac OS X

Details

We need to update the validator data once we've tagged 1.11 final.
Blocks: 802712
(Assignee)

Comment 1

6 years ago
https://github.com/mozilla/amo-validator/pull/185 has the new hashes, and verified that 1.11 is listed in there.

We're releasing 1.11 on Tuesday, so the sooner we can get this in, the better.

I'm setting the milestone to Nov 1, but that'll leave two days where the new SDK is released, but AMO will complain. Is there any way we can get this pushed earlier than Thursday?


Also, I ran the update script from an up to date branch, which should include the new stuff to pick up the pickle file as explained in bug 784553 comment 4, but I don't see a pickle file anywhere in there.

There were also 41 errors and 135 failures when the script exited, so I'm not sure if everything ran correctly.

Am I still doing something wrong, or is that how it should work, Matt?
Status: NEW → ASSIGNED
Flags: needinfo?(mattbasta)
Target Milestone: --- → 2012-11-01

Comment 2

6 years ago
Merged the code, will update the pickle file myself.

Not sure if we can get this pushed before Thursday. That's something to ask clouserw.
Flags: needinfo?(mattbasta)

Comment 3

6 years ago
Bumped in zamboni:

https://github.com/mozilla/zamboni/commit/beab7aa14edcdb45de1713c61c42591f5c2411ce
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Thanks :basta! TBC: Thursday is fine, as the validator will just display a warning: "this add-on uses a future version of the SDK: 1.11" in the meantime, correct?
No worries. 

And yes, it should.
(Assignee)

Comment 6

6 years ago
1.11-based addon passed the validator with no warnings or errors, looks like it's all set!
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.