Release Management/New Hire Portal: Difference between revisions

Jump to navigation Jump to search
Line 65: Line 65:


= Wednesday =
= Wednesday =
* Start idling in #mobile
* You should already be idling in #mobile
* Attend the mobile meeting in the morning at 9:30AM in WarpCore (starting to see a trend here?). Add an agenda item to the meeting introducing yourself to the mobile team. All a bunch of really good, hard working guys/gals.
* Attend the mobile meeting in the morning at 9:30AM in WarpCore (starting to see a trend here?)  
* Sign up for https://lists.mozilla.org/listinfo/dev-platform (archive at https://groups.google.com/group/mozilla.dev.platform/).
** Add an agenda item to the meeting introducing yourself to the mobile team
* Platform meeting at 11AM in WarpCore
* Sign up for more mailing lists:
* If you got syndicated on Mozilla Planet, great, get your first blog post up introducing yourself to the community/company. Run it by Lukas if you want to doube-check tone. Things to include may be where you're coming from, why you're excited about Mozilla, and something you do outside of work.
** [https://lists.mozilla.org/listinfo/dev-platform Dev-Platform]
* Start learning HG (Mercurial). Of particular interest are how to check in changes, commit them, back them out, and transplant them. Take notes for the next person on the team.
** [https://mail.mozilla.org/listinfo/enterprise Enterprise]
* Join Lukas for triage (check with her when this will be held, it moves around)
** [https://mail.mozilla.org/listinfo/b2g-test-drivers B2G Test Drivers]
* Lukas will explain tracking flags, branch approval flags, and introduce you to the Etherpad of bug lists https://etherpad.mozilla.org/relman-bugs-lists
* Platform meeting at 11AM in the Product Coordination Vidyo room
* Try to start soaking in Lukas's intuition (from your interview I know it's already good), next week you'll start shadowing branch triage and making recommendations.
* If you got syndicated on Mozilla Planet, great, get your first blog post up introducing yourself to the community/company
** Things to include may be where you're coming from, why you're excited about Mozilla, and something you do outside of work
* Start learning HG (Mercurial)
** Of particular interest are how to check in changes, commit them, back them out, and transplant them
** [http://hgbook.red-bean.com/ This book] is a great place to start
** When you think you have the handle on it - check out one of our use cases: [https://wiki.mozilla.org/Release_Management/Merge_Documentation Merge Day] and see if you can do a fake merge locally
* Join RelMan team for triage (currently 12-2pm) where we burn through [https://etherpad.mozilla.org/relman-bugs-lists our tracking priorities list]
* You will learn about FLAGS:
** tracking
** status
** approval
** keywords
* Try to start soaking your teammate's intuition (from your interview we know it's already good), next week you'll start shadowing branch triage and making recommendations
 
= Thursday =
= Thursday =
* Start familiarizing yourself with the Bugzilla/LDAP APIs. Ask Lukas for pointers on the best documentation.
* Start familiarizing yourself with the Bugzilla/LDAP APIs. Ask Lukas for pointers on the best documentation.
Confirmed users
4,467

edits

Navigation menu