Hi On 07.11.2013 13:00, Ed Morley wrote: > b) [My preference]: First make a gaia change to disable the tests (or > make them feature-detect so they are backwards-compatible), then once > that's on mozilla-central, land the gecko change on b2g-inbound (since > the travis run will be green), then once that is on mozilla-central land > another gaia change to remove the support for the previous API/...
This worked quite well when I added an API and changed Gaia to use it. But I remember having a separate bug for each step, which was a bit of an overhead for a rather simple change. > Unless anyone has any other ideas? I'd rather support the idea of moving Gaia into the Gecko repository. That would probably remove some issues of compatibility that show up every now and then, and it would make landing bugs that change both easier. > Also - what do we think about getting Travis to use the b2g-inbound > builds rather than mozilla-central? (In order to reduce the cycle time > when needing to make gecko changes) I think b2g-inbound breaks too often. How would Travis know which version is not broken and contains the necessary changes to Gecko? Best regards Thomas > Best wishes, > > Ed > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
