canmove, Confirmed users
1,126
edits
Release Management/Release Process/FAQ: Difference between revisions
Release Management/Release Process/FAQ (view source)
Revision as of 16:48, 21 December 2014
, 21 December 2014Bug 1082602
(Created page with "= Frequently Asked Questions = == Q) Do I need to have a tracking flag set on every bug that may have to land on a firefox channnel ? == A) NO. This is often a common misconc...") |
m (Bug 1082602) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
'''All changes''' must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. You must check the tree before pushing, and watch the tree for failures after pushing.You may have to backout based on any new test failures your patch caused or if we identify a new regression which is critical for us to solve and there is risk in taking a forward fix based on where we are in thee current release cycle we may request a backout | '''All changes''' must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. You must check the tree before pushing, and watch the tree for failures after pushing.You may have to backout based on any new test failures your patch caused or if we identify a new regression which is critical for us to solve and there is risk in taking a forward fix based on where we are in thee current release cycle we may request a backout | ||
== Q) Dealing with unexpected failures on | == Q) Dealing with unexpected failures on Treeherder ? == | ||
Check [https://developer.mozilla.org/en-US/docs/Developer_Guide/Committing_Rules_and_Responsibilities#Dealing_with_test_failures this page for more info] | Check [https://developer.mozilla.org/en-US/docs/Developer_Guide/Committing_Rules_and_Responsibilities#Dealing_with_test_failures this page for more info] | ||
== Q) How many beta's do we have per Firefox Release cycle ? == | == Q) How many beta's do we have per Firefox Release cycle ? == | ||
In a traditional cycle you can expect six beta's per cycle. But we may sometimes | In a traditional cycle you can expect six beta's per cycle. But we may sometimes spin additional beta's if needed for any critical change that may be necessitating further betas. | ||
== Q) Can I wait till the last beta to get my patch landed ? == | == Q) Can I wait till the last beta to get my patch landed ? == | ||
| Line 43: | Line 43: | ||
* Fixes for top-crashes | * Fixes for top-crashes | ||
* Fixes for regressions | * Fixes for regressions | ||
* Backouts if the investigation leads its a better alternative if forward fixes are risky depending on | * Backouts if the investigation leads its a better alternative if forward fixes are risky depending on how close we are to the end of cycle. | ||
* Any low risk uplifts for bugs that are not tracked but may help improve our product | * Any low risk uplifts for bugs that are not tracked but may help improve our product | ||
* Landing tests that may help a feature with no impact to existing test framework | * Landing tests that may help a feature with no impact to existing test framework | ||
| Line 58: | Line 58: | ||
== Q) Is there an easy I could implement channel specific features that may be categorized as new/experimental/may not be ready for release ? == | == Q) Is there an easy I could implement channel specific features that may be categorized as new/experimental/may not be ready for release ? == | ||
We have recently been helped by Gavin Sharp to be able to have Channel-specific build defines which helps control the feature per channels in a better way and may fit the use case here. Check [https://wiki.mozilla.org/Platform/Channel-specific_build_defines wiki] on implementation details . This really helps in cases where features that require going to aurora/beta to gather impact before ship, but not ready for immediate release to be configurable | We have recently been helped by Gavin Sharp to be able to have Channel-specific build defines which helps control the feature per channels in a better way and may fit the use case here. Check [https://wiki.mozilla.org/Platform/Channel-specific_build_defines <B>wiki</B>] on implementation details . This really helps in cases where features that '''require''' going to aurora/beta to gather impact before ship, but not ready for immediate release to be configurable | ||