ReleaseEngineering/Releaseduty/FAQ: Difference between revisions

Jump to navigation Jump to search
Add answers to question number 10
(Add answers to question number 16)
(Add answers to question number 10)
Line 66: Line 66:
<code>TODO answer</code>
<code>TODO answer</code>


10. '''What is a partner repack change for FF?''' What does "partner" refer to in this context? (e.g. Bug 1231679)
10. '''What is a partner repack change for FF?''' What does "partner" refer to in this context? (e.g. {{bug|1231679}})
 
Partner repacks refer to 3rd party customized branded versions of Firefox that Mozilla is taking care of for some of its clients. With some exceptions, most of the partner reconfigs lie under private repositories. For example, whenever we ship a build release on our servers, we also take care and host a Bing repack. For the others that we don't publish, all the resulting artifacts are private. Mostly, the partner repacks don't need too much of RelEng interference as all bits are held under private git repos and are directly handled by the partnering companies. The usual first occurrence with them for a releaseduty is when releases may get some delays in being published through the ''<channel>-cdntest'' because some of the partner-repacks are still running, hence holding the checksums step which at its turn holds the push-to-mirrors step.


<code>TODO answer</code>


11. During the release-drivers meeting, people often refer to conversations noticed on Twitter (as in complaints or positive feedback on something). How do people know what's on Twitter? '''Is there a specific handle or hashtag they're following or it's just the @mozilla and related conversations?'''
11. During the release-drivers meeting, people often refer to conversations noticed on Twitter (as in complaints or positive feedback on something). How do people know what's on Twitter? '''Is there a specific handle or hashtag they're following or it's just the @mozilla and related conversations?'''
Confirmed users
391

edits

Navigation menu