Bumping gaia.json for 2 gaia revision(s) a=gaia-bump
authorB2G Bumper Bot <release+b2gbumper@mozilla.com>
Fri, 28 Nov 2014 22:47:04 -0800
changeset 243929 1ff2b15d69cb0fe5961513d8598dcd0610817fab
parent 243928 3477ca12357a4b8af68d3958cc497491dedfbb72
child 243930 b362bcbfea14c41038ed22d04fbdf545cdc34450
push id4489
push userraliiev@mozilla.com
push dateMon, 23 Feb 2015 15:17:55 +0000
treeherdermozilla-beta@fd7c3dc24146 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersgaia-bump
bugs26566, 1097421
milestone37.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bumping gaia.json for 2 gaia revision(s) a=gaia-bump ======== https://hg.mozilla.org/integration/gaia-central/rev/cdbaff53710b Author: Andrew Sutherland <asutherland@asutherland.org> Desc: Merge pull request #26566 from asutherland/upgrade-emailjs Bug 1097421 - [email] Upgrade email.js omnibus bug. r=jrburke ======== https://hg.mozilla.org/integration/gaia-central/rev/c420852c9ac3 Author: Andrew Sutherland <asutherland@asutherland.org> Desc: Bug 1097421 - [email] Upgrade email.js omnibus bug. r=jrburke Land https://github.com/mozilla-b2g/gaia-email-libs-and-more/pull/353 See its individual commit comments and the bugs dependent on bug 1097421 for more info. Note that this also includes 2 autoconfig changes: - 126.com: This makes us consistent with 163.com, another mail domain also operated by netease which also uses the coremail mail server and whose ActiveSync implementation does not work so well with our implementation. This avoids its autodiscover exposure capturing us and causing us to use its ActiveSync implementation. This is basically required since the Mozilla ISPDB is not capable of overriding the ISP's entries. (Which is desired in most cases for many reasons, but being able to say "don't use that ActiveSync implementation!" would be helpful.) - yahoo.co.jp: Right now the ISPDB says to use POP3. Only with these fixes do we work with yahoo.co.jp's IMAP implementation, so (selfishly), it's better to do this for now than to change the ISPDB.
b2g/config/gaia.json
--- a/b2g/config/gaia.json
+++ b/b2g/config/gaia.json
@@ -1,9 +1,9 @@
 {
     "git": {
         "git_revision": "", 
         "remote": "", 
         "branch": ""
     }, 
-    "revision": "c051a00f86ce3f1f040565a6b9f074cac375ecdd", 
+    "revision": "cdbaff53710b14fcc1eb64781e36d66a9925a3d8", 
     "repo_path": "integration/gaia-central"
 }