Release Management/Day 1 Checklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (→‎Account Permissions: added one more ldap group for svn)
(moved to 'Onboarding' wiki page, added a redirect)
Line 1: Line 1:
Welcome to Release Management.
#REDIRECT [[Onboarding]]
 
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:
* Bugs
** Request for your bugzilla account to be added to mozilla-next-drivers and mozilla-stable-branch-drivers groups in order to set tracking flags -- file a bug (eg: {{bug|962151}}), {{bug|1135168}}. 
** [http://www.mozilla.org/en-US/about/governance/policies/security-group/bugs/#expanding Security permission] comes later.
* Repos
** svn commit access to http://viewvc.svn.mozilla.org/vc/projects/ for modifying product-details-- file a bug (eg: {{bug|962171}}, {{bug|1137251}}, {{bug|1135512}}) You will need specific allows for /libs/product-details,
/projects/mozilla-europe.org and /projects/mozillaonline.com.  And, you will need to be in the svn_mozilla LDAP group.
 
If this is going to be a regular set of requests it would probably be better to
create a group for them.
** 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) You will need two [https://wiki.mozilla.org/Modules/All#Core owners or peers for a core hg module] to vouch for you as described in [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Commit Access Policy].
 
* Communications
** admin permissions for https://relman.etherpad.mozilla.org
* Builds
** Ask to be added to the LDAP group called ''verbatim'' by filing a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=Infrastructure%3A%20LDAP Infrastructure & Operations::Infrastructure:LDAP]. This will give you permission to access to https://l10n.mozilla.org/
** Ask to be added to the groups ''shipit'' and ''vpn_shipit'' to get access to the build tool & l10n, by filing a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=Infrastructure%3A%20LDAP Infrastructure & Operations::Infrastructure:LDAP]. Example: {{Bug|1135198}}
** Request Mozilla VPN access (required to access ship-it)
* Release Notes
** Request admin access to https://nucleus.mozilla.org by filing a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=Nucleus Websites::Nucleus]. Example: {{Bug|1135186}}
 
=Communication Channels=
==Release Calendar==
* https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
 
==E-Mail==
Note that some of these mailing lists need approval from an administrator.
 
*release-mgmt@mozilla.com - contact IT to be added (servicedesk@mozilla.com or on ServiceNow)
*release-drivers - visit https://mail.mozilla.org/listinfo/release-drivers to add yourself to release-drivers@ once your email is working
*security-group - visit https://mail.mozilla.org/listinfo/security-group to add yourself to security-group@ once your email is working
*Send a test message to both addresses individually to verify that your address has been added/subscribed.
 
You'll need to manually subscribe to
 
*mozilla.dev.planning - visit https://lists.mozilla.org/listinfo/dev-planning
*mozilla.dev.tree-management - visit https://lists.mozilla.org/listinfo/dev-tree-management
*Enterprise - visit https://mail.mozilla.org/listinfo/enterprise
*Stability - vist https://mail.mozilla.org/listinfo/stability
 
These are available as [news://news.mozilla.org newsgroups], google groups, and [https://lists.mozilla.org/listinfo Mailman lists]
 
==Websites==
 
* [https://metrics.mozilla.com/pentaho Metric] (TODO: this url is out of date)
* [http://crash-stats.mozilla.com/ Crash reports]
 
== 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 [https://intranet.mozilla.org/StaffMeeting]]
** #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 <tt>irssi</tt> under screen to get continuous view of traffic. Ask around.
 
See [[#pastebin|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
* https://relman.etherpad.mozilla.org for team-specific information
* https://etherpad.mozilla.org/firefox38-worry-list Worry list specific to each release (change the version in the url as needed)
 
==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 [http://hg.mozilla.org/build/braindump/file/tip/utils/pastebin 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==
 
# Please download & install Firefox [http://www.mozilla.org/fr/firefox/channel/#aurora aurora], [http://www.mozilla.org/fr/firefox/channel/#beta beta] and [http://www.mozilla.org/fr/firefox/channel/#firefox release]
# [https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles#w_creating-a-profile Create new profiles] for each version + your own profile. Read [https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles Multiple Firefox Profiles] for more help with the profile manager.
 
==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==
* [[Release_Management]]
* [[Firefox/Channels/Meetings]]
* [https://www.mozilla.org/en-US/firefox/organizations/faq/ ESR FAQ]
* [[Enterprise/Firefox/ExtendedSupport:Proposal]]
* [[Release_Management/ESR_Landing_Process]]
 
==Bugzilla ==
* Install Akeybl's [http://alex.keybl.com/?p=23 bugzilla service] and HTML page title copy [https://builder.addons.mozilla.org/addon/1018034/ addon]
* Configure the [https://bugzilla.mozilla.org/userprefs.cgi?tab=securemail securemail] section if you want to see the content of security bugs in your email client. GPG key or [http://kb.mozillazine.org/Getting_an_SMIME_certificate SMIME certificate] are accepted.
 
=== Reports ===
* [https://bugzilla.mozilla.org/page.cgi?id=release_tracking_report.html release tracking report]
=== Queries ===
In your bugzilla preferences, under Saved Searches, you can add some of the following to your footer for quick access:
* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=approval-aurora%3F&sharer_id=272375 approval-aurora?]
* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=approval-beta%3F&sharer_id=272375 approval-beta?]
* [https://bugzilla.mozilla.org/buglist.cgi?o1=equals&v1=%3F&known_name=tracking-ff32%3F&f1=cf_tracking_firefox37&query_based_on=tracking-ff32%3F&query_format=advanced&list_id=12037223 tracking_firefox37?] (adjust for current beta version as needed)
* [https://bugzilla.mozilla.org/buglist.cgi?v4=---&f1=cf_tracking_firefox37&o3=equals&v3=affected&j2=OR&o1=equals&f4=cf_status_firefox37&query_format=advanced&f3=cf_status_firefox37&o4=equals&f2=OP&v1=%2B&list_id=12013780 Firefox 37 tracked bugs] (Make sure to query for the resolved bugs as well as open ones)
 
=Tools=
==Repos to check out==
* [https://github.com/lsblakk/relnotes Release Notes generation] (TODO: out of date: now done in nucleus?)
* [https://github.com/mozilla/bztools Bugzilla API scripts]
* [https://github.com/bbajaj/relman_nag_tool nag tool]
* [http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/ svn repo for web pages]
* [http://harthur.github.io/mozregression/ mozregression]
 
= 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 ==
* Request here https://bugzilla.mozilla.org/show_bug.cgi?id=391268
 
[[category:Release_Management|*]]

Revision as of 01:01, 6 March 2015

Redirect to:

Retrieved from "https://wiki.allizom.org/index.php?title=Release_Management/Day_1_Checklist&oldid=1060187"