Release Management/Day 1 Checklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Removed autoland checklist step)
Line 11: Line 11:
** svn commit access to http://viewvc.svn.mozilla.org/vc/projects/ for modifying product-details-- file a bug (eg: {{bug|962171}})
** svn commit access to http://viewvc.svn.mozilla.org/vc/projects/ for modifying product-details-- file a bug (eg: {{bug|962171}})
** hg commit access (scm_level3) -- read http://www.mozilla.org/hacking/committer/, fill out a committer agreement, file a bug (eg: {{bug|738713}} except you'll request commit access, not elevation of current permissions)
** hg commit access (scm_level3) -- read http://www.mozilla.org/hacking/committer/, fill out a committer agreement, file a bug (eg: {{bug|738713}} except you'll request commit access, not elevation of current permissions)
** [not in use right now] request addition to autoland group permission in Bugzilla (current admin for this is lsblakk)
 
* Communications
* Communications
** admin permissions for https://relman.etherpad.mozilla.org
** admin permissions for https://relman.etherpad.mozilla.org

Revision as of 19:11, 20 February 2015

Welcome to Release Management.

Here's a list of accounts to set up, tools to check out, and any other details we can think of to help you start getting yourself set up.

Account Permissions

You'll want to make sure you have the necessary permissions to do the following and some will take longer than others to achieve so start early:

  • Communications
  • Builds
    • Go on IRC #infra channel (look for the keep in the Mozilla intranet) and ask to be added to the LDAP group called verbatim. This will give you permission to access to https://l10n.mozilla.org/
    • Still on #infra, ask to be added to the group shipit too to get access to the build tool & l10n.
    • Request Mozilla VPN access (required to access ship-it)
  • Release Notes

Communication Channels

Release Calendar

E-Mail

Note that some of these mailing lists need approval from an administrator.

You'll need to manually subscribe to

These are available as newsgroups, google groups, and Mailman lists

Websites

IRC

  • https://wiki.mozilla.org/IRC irc://irc.mozilla.org
  • irc.mozilla.org:6697
    • #airmozilla - back channel for public broadcasts
    • #developers - monitor check-ins and speak with devs
    • #fx-team - good place to speak with desktop team
    • #mobile - good place to speak with mobile devs
    • #moco [access_key is here [1]]
    • #planning - back channel for product coordination meeting, good place to speak with broader product team
    • #pm - Sheila's org
    • #release-drivers - release related discussions
    • #releng - releng team channel
    • #relman - our team channel
    • #security (ask for channel key) - the security team's channel
    • #qa - QE team channel
    • #www - for speaking with the mozilla.org team in case a push breaks or otherwise doesn't work
  • http://chatzilla.hacksrus.com/faq/#connect

Many folks run a BNC (an IRC bouncer) (e.g. znc) and/or irssi under screen to get continuous view of traffic. Ask around.

See below for a local pastebin install, so you don't paste huge amounts in channel.

EtherPAD

EtherPad is a great tool for dynamic collaboration during meetings, brainstorming, or other times when you need to collaborate: https://etherpad.mozilla.org/ for general use

Pastebin

There's a local pastebin instance at http://pastebin.mozilla.org/, so you don't need to paste multi-lines into a channel. Use this handy helper script to pipe to pastebin from terminal. 

   it creates a new page from stdin, and outputs the url to stdout
   an argument will be interpretted as the syntax highlighting format to use
   sample usage: hg diff | pastebin python | pbcopy (last part mac specific)
   set & export PASTEBIN_NAME if you don't want to post as anonymous.

Planet

Add a bug similar to bug 605709 to get your blog syndicated on http://planet.mozilla.org. You can choose to send every post, or create a feed for a custom tag (eg: 'mozilla'). Having your blog syndicated to planet is a great channel for announcing new features (along with tweeting and posting to newsgroups).

Software

Firefox

  1. Please download & install Firefox aurora, beta and release
  2. Create new profiles for each version + your own profile.

VPN

  • Configure your system to access to the Mozilla VPN in order to get access to internal tools.
  • Then, report a bug in Infrastructure & Operations: Mozilla VPN: ACL requests to get the ACL to ship-it and bedrock.productdetail. Example: bug 986037 and bug 1001632
  • Request permissions on bedrock.productdetail (it is not connected to the LDAP). ping TODO
  • Note that using the Mozilla DNS servers is necessary to resolve the necessary URLs

Handy Links

How To and Oft-Used

Bugzilla

Reports

Queries

In your bugzilla preferences, under Saved Searches, you can add some of the following to your footer for quick access:

Tools

Repos to check out

Fun Tips & Tricks

Vidyo Conference Rooms

Sometimes when you're on the go and you need to dial into a vidyo room, you may not have time to find the info and having it already loaded in your phone can make a difference. Your RelMan teammates might be able to beam you the contact info from their phones, or you can add them yourself like this:

  • Vidyo; Warp Core 6509030800,92,5312#

Rooms to mark as favourites and contacts: Spadina (Toronto), Release Coordination (Virtual room, no physical location)

Subcribe to funstuff

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Release_Management/Day_1_Checklist&oldid=1057249"