Platform/2015-01-13: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 18: Line 18:
<small>(Release and system issues that may impact engineering this week.)</small>
<small>(Release and system issues that may impact engineering this week.)</small>


===Notices/Schedule (lsblakk/sylvestre/lmandel)===
===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|-
Line 39: Line 39:
A note on branching:
A note on branching:
* FXOS v2.2 update : Please note that has diverged from mainline gecko and is on its own b2g37 branch. mozilla-aurora (gecko 37) will continuously be merged to mozilla-b2g37_v2_2 . So, if you have a gecko bug that you are fixing on aurora and impacts b2g as well, you do not have to worry about requesting approval twice as the sheriff's will auto-merge it for you.
* FXOS v2.2 update : Please note that has diverged from mainline gecko and is on its own b2g37 branch. mozilla-aurora (gecko 37) will continuously be merged to mozilla-b2g37_v2_2 . So, if you have a gecko bug that you are fixing on aurora and impacts b2g as well, you do not have to worry about requesting approval twice as the sheriff's will auto-merge it for you.
* Want all merge and release days included in your calendar? Add this [https://www.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939%40resource.calendar.google.com Google calendar].


<!-- 1. What has your team done since last week that might impact others? -->
<!-- 1. What has your team done since last week that might impact others? -->
Confirmed users
2,473

edits

Navigation menu