Closed Bug 857049 Opened 11 years ago Closed 11 years ago

Port Twitter API v1.1 from Instantbird to c-c

Categories

(Thunderbird :: Instant Messaging, defect)

defect
Not set
normal

Tracking

(thunderbird21+ fixed, thunderbird22 fixed, thunderbird-esr1721+ fixed)

RESOLVED FIXED
Thunderbird 23.0
Tracking Status
thunderbird21 + fixed
thunderbird22 --- fixed
thunderbird-esr17 21+ fixed

People

(Reporter: clokep, Assigned: clokep)

References

()

Details

Attachments

(1 file)

See also bug 842183 and friends.

API v1 of twitter is being retired on May 7th [1]. Instantbird has been updated to v1.1 [2] (the newest version), these changes should be ported to Thunderbird (and probably into the newest version as possible, beta or aurora?) After this date, users of Thunderbird will be unable to connect to Twitter.

This also requires a change to http.jsm. (mconley has already tested this change and approved it.)

What is the status of Thunderbird releases? How can we get this out quickly? Should this be included in an ESR branch?

[1] https://dev.twitter.com/blog/api-v1-retirement-final-dates
[2] https://bugzilla.instantbird.org/show_bug.cgi?id=1890
Attached patch PatchSplinter Review
This is a port of the Instantbird changeset [1], with the http.jsm changes also applied to mail/base/modules/http.jsm. Unfortunately I didn't have a c-c build that was anywhere close to up to date and this is going to take a while to build...so this is currently "untested" (as part of TB, IB nightlies have been running with a similar patch for a while), but will be tested as soon as I can get my build running.

[1] http://hg.instantbird.org/instantbird/rev/743ce473ff0a
Assignee: nobody → clokep
Status: NEW → ASSIGNED
Attachment #732631 - Flags: review?(florian)
Attachment #732631 - Flags: review?(mconley)
Comment on attachment 732631 [details] [diff] [review]
Patch

rs=me for the port from the Instantbird repository. The code has already been r+'ed by the relevant chat/ peers (including me) in https://bugzilla.instantbird.org/show_bug.cgi?id=1890.

Would still be good to have Mike's review for mail/base/modules/http.jsm (he only gave feedback+ in the Instantbird bug).
Attachment #732631 - Flags: review?(florian) → review+
Comment on attachment 732631 [details] [diff] [review]
Patch

Review of attachment 732631 [details] [diff] [review]:
-----------------------------------------------------------------

Yeah, this is totally fine. Let's roll with this.
Attachment #732631 - Flags: review?(mconley) → review+
https://hg.mozilla.org/comm-central/rev/d39a8d280ac3
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment on attachment 732631 [details] [diff] [review]
Patch

[Triage Comment]
Ok, lets get this on Aurora and Beta for some accelerated testing as we'll need this soon.
Attachment #732631 - Flags: approval-comm-beta+
Attachment #732631 - Flags: approval-comm-aurora+
Comment on attachment 732631 [details] [diff] [review]
Patch

[Triage Comment]
I've not heard of any issues, so lets push forward to ESR as well so that we're ready.
Attachment #732631 - Flags: approval-comm-esr17+
Comment on attachment 732631 [details] [diff] [review]
Patch

Unfortunately this patch doesn't apply cleanly to comm-esr17, can someone take a look at doing a patch before early next week? Thanks.
Attachment #732631 - Flags: approval-comm-esr17+ → approval-comm-esr17-
Ping, has anyone had time to do this?
Ok, I think I've unbitrotted this correctly and pushed it here:

https://hg.mozilla.org/releases/comm-esr17/rev/a63b6053d11c

If poss, please review/try it out, I'll be trying it in a bit once the builds complete.
I've tested as best as I can, and I still seem to receive tweets and things, so hopefully the merge was successful. If others can please test esr branch before we release on Tuesday, that'd be really useful.
Target Milestone: --- → Thunderbird 23.0
(In reply to Mark Banner (:standard8) from comment #10)
> Ok, I think I've unbitrotted this correctly and pushed it here:
> 
> https://hg.mozilla.org/releases/comm-esr17/rev/a63b6053d11c
> 
> If poss, please review/try it out, I'll be trying it in a bit once the
> builds complete.

This looks fine! Thanks for doing this. Sorry I couldn't get to this earlier, I was traveling without a computer for the past two weeks.
You need to log in before you can comment on or make changes to this bug.