Confirmed users
976
edits
Release Management/Release Process/FAQ: Difference between revisions
Release Management/Release Process/FAQ (view source)
Revision as of 18:28, 23 May 2013
, 23 May 2013→Q) Is there an easy I could implement channel specific features that may be categorized as new/experimental/may not be ready for release ?
| 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 <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 | 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 | ||