2007-07-23T19:34:08Z

Zachlipton: /* QA */

[[WeeklyUpdates/2007-07-16| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2007-07-30|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 4, 2007)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* join irc.mozilla.org #staffmeeting for attendance taking and backchannel

'''note:''' all participants are muted automatically; if you want to talk, press *1 to un-mute yourself

= In Attendance =

= Development Updates =

== Fx/TB 1.5.0.13/2.0.0.5 ==

== TB 3 ==
* We're working on final approval for switching our spell check engine to hunspell for Firefox and Thunderbird. Please let us know if you have any concerns.
* We're spending a lot of time looking at memory leaks right now and could use extra help tracking some leaks down (using the XPCOM_MEM_LEAK_LOG environment variable). Especially with the compose window. Please see David or Scott if you are interested in helping out.

== Gecko 1.9 ==

* M7 Gecko Feature Freeze July 25th.
* Major New Features:
** Anti-Malware
** Finalized Offline APIs
** Secure Wrappers

== Firefox 3 ==

== IT ==

== Build ==

== QA ==
Test Exectuion
* Completed FFX 2.0.0.5 and TBird 2.0.0.5 security releases [juan, tomcat, tracy, al, others]

Tools and Autoamtion
* [http://quality.mozilla.org/projects/automation/talos Talos Performance Project]
** Collecting Trunk baselines. Had trouble getting new pageset running on old trunk builds. Switched qm-pxp02 to old page set, baseline currently being collected. We currently have baseline data for windows trunk from april 2006 - october 2006 woo! [alice]
** Talos found a performance regression! [http://graphs.mozilla.org/graph.html#spst=range&spstart=1183084407&spend=1185212524&bpst=cursor&bpstart=1183084407&bpend=1185212524&m1tid=7&m1bl=0&m1avg=0 A visible leap in the tp loadtime numbers] was found, regression window was determined, patch was pinpointed and backed out and tp numbers were seen to improve
** Macport reviewed and landed in cvs. [zach, alice]

== Security ==

== Marketing/PR ==
* OSCON:
** [http://www.spreadfirefox.com/node/27794/ Community party]: Grab some flyers before you go and spread the word.
** New [http://conferences.oreillynet.com/cs/os2007/view/e_sess/14879/ "Get involved with Mozilla" BoF] scheduled
** Booth folks still needed

== Community ==

== Mozilla Labs ==

== Developer Relations ==
* Headed to OSCON (shaver, mfinkle, jresig and fligtar)
* WebRunner experimentation continues
** Adding spellcheck suggestions and password support
** Better external link detection
** Creating an extension to manage webapps from Firefox
** Exploring the use of Firefox3 as a runtime for WebRunner
* Demo round-up: Compiling a list of demos we'd like to have:
** Showcase Firefox3 features
** "Web of the future" features

== Webdev, Add-ons, AMO ==

= Foundation Updates =

= Foundation Updates =

Note that Frank is traveling to Portland today for OSCON and won't be participating in the weekly call.

* Grants and related activities
** Henri Sivonen completed another milestone in his Mozilla Foundation-funded [http://about.validator.nu/ HTML5 conformance checker] project.

* IP/legal issues
** Frank and Gerv did some internal licensing-related stuff.

* Other
** Frank was on vacation and traveling a good part of the week.
** Zak has been working to help get the [http://cyber.law.harvard.edu/ipg Internet as a Public Good symposium] organized.
** David has been working on various tasks related to donations to the Mozilla Foundation.
** Gerv attended the [http://cups.cs.cmu.edu/soups/2007/ Symposium on Usable Privacy and Security] (SOUPS).

For more information see the individual status reports from [http://davidwboswell.wordpress.com/ David], [http://hecker.org/mozilla/foundation-activities-2007-07-20 Frank], [http://weblogs.mozillazine.org/gerv/ Gerv], and [http://zak.greant.com/ Zak].

= Roundtable =

= Other Business =

Performance/Status Meetings/2007-July-18

2007-07-18T15:01:36Z

Zachlipton: /* Infrastructure */

[[Performance/Status_Meetings|« Back to Status Meetings ]]

== Participants ==

== Infrastructure ==
* Generate reliable, relevant performance data (already underway as talos). Talos status update?
http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest

* Areas where help is needed
* Discuss talos cpu usage metric (zach)
* expand the scope of performance testing beyond Ts/Tp/TXUL/TDHMTL
* reduce noise in tests to ~1% (suggested by bz, not started)
* move perf tests to chrome, so we get more reliable results, and can test more than just content
* improve performance reporting and analyses:
** Better reports for sheriffs to easily spot perf regressions
** Tracking down specific performance issues
* stats change to track AUS usage by osversion.

*Priorities for infra:
** Generate historical baselines
** General profile data regularly on builds
** Getting the perf numbers more stable
** Developing the graph server to display time spent in each module

* New ideas
** Question: How are we tracking perf bugs, specifically, and are we doing this the same way we are triaging security bugs? Can we do it the same way if not? (damon)

== Agenda ==

== Gecko: Perf discussion ==

* Perfathon update
** vlad failing to provide data
** vlad will do so by next wednesday, because even if I had started uploading useful data the upload probably wouldn't have finished by then (sorry!)

* pageload test rewrite ([https://bugzilla.mozilla.org/show_bug.cgi?id=387110 bug 387110])
** since we have a chance at a clean break, we should look at how the composite scores are calculated
** do we still want to ignore the biggest value when computing the mean and stddev? (there is caching and stuff that happens during the first time a page is loaded that ends up beneficially effecting subsequent page loads)
** do we want to more cycle more intelligently?
*** e.g. do we want to keep cycling (up to some max) until the stddev drops below some number?
*** do we want to try to intelligently throw outliers out?

* update on [https://bugzilla.mozilla.org/show_bug.cgi?id=363258 timer resolution on windows] from Rob Arnold.
* Talos results
** What's it look like for 1.8 -> 1.9?

* Todo: verification of test results
** '''Fonts, valid rendering, etc.'''
** '''TODO: Stuart: verify that concerns about talos results are addressed'''

* probe update
** vlad spoke with Sun guys
** will work with them to integrate XP-probes and dtrace probes into (most likely) a new toplevel module
** then will present to module owners and show demos
*** hopefully can convert per-module tracing schemes into probes
*** Sun guys would be happy to come out and do a presentation of dtrace-in-mozilla and give an idea of what can be done with dtrace itself and the scripts
** dtrace should probably be on by default in our builds if dtrace is possible
*** not sure about OSX -- can we build with dtrace enabled and still run on 10.4?
** xp probes should be off, but possibly on in our tinderbox/nightly builds
*** vlad to investigate perf impact

=== Previous weeks ===

* jrpof tinderbox

* synthetic tests (TODO)
** put specific tests into talos framework
** poach mochitest performance tests
** individual reftest-like items

* need to get a bunch of people looking at profiles (TODO)
** take up some of these meetings to sit down and look at profiles
** timer-based profiling is better (vtune/jprof/oprofile/etc., not quantify)
** TODO: vlad to generate profile for next week's meeting

* running without Fx chrome
** new pageloader stuff can do this

* examining default theme for performance issues

* Tp vs. Tp2
** new pageloader stuff avoids this problem
** Tp2 was flawed in some ways -- one big one is that it loaded pages in an iframe, so initial paint delay was never coming into play, and we were potentially reflowing more thannecessary

== Other Information ==

[[Performance/Status_Meetings/Related_Bugs|Related Bugs]]

Litmus:Extension

2007-07-16T23:23:46Z

Zachlipton: /* Content pulled from external urls */

= Key Links =
* See the project [http://www.zachlipton.com/extensionStatus/ Status Page]
* [[Litmus:Extension/Notification|Notification system design]]

= Current Status =
The [http://www.zachlipton.com/extensionStatus/ Status Page] (updated from time to time) has Zach's detailed task list, a broad overview is below:
* General
** Everything needs theming/styling/beautification
** Content!
* Feature Areas
** QMO Tab
*** Feeds are all being updated live from QMO, created a couple of custom QMO views for the various content areas
** Litmus Tab
*** Mockup and testcase retrieval are in place and working. Result submission is almost working
*** Need design and implementation for testgroup selection and other work in this area
** Bugzilla Tab
*** It's displaying a static page on QMO for now, need to write content (links to docs)
** Chat Tab
*** Chatzilla is bundled with the extension. Clicking the chat button launches a chat window and connects to irc
** Settings Tab
*** Preferences for Litmus account info and notifications are built and working. Litmus account gets validated before saving.
*** Need opsys/platform/locale settings
** Help Tab
*** Will be a static page hosted on QMO like the Bugzilla tab. Need content.
** Initial Setup
*** Mostly complete, have account creation, existing account login, settings
*** Settings needs a little more work
*** Account creation code needs to be secured
** Notifications
*** Specification complete and on the wiki. Need to implement and need to design Hermes (notification server)

= Initial Mockups =
See some screencaps at [http://zachlipton.com/qaExtensionMockups]

= Goals =
* Make it easier for new testers to get started
* Allow testers to view tests and submit results from a separate window inside the app
* Make testers feel valued and encourage them to keep testing
* Help integrate testers into the community
* Encourage participation in special events (testdays, pre-release testing, etc...)

= Feature Areas =
* Initial setup
** Helps users get setup with an account if they don't already have a Litmus account. Provides an introduction to Mozilla QA, what we do, how testing works.
** One guided process from installing the extension to submitting their first test result, real easy and welcoming
* Running tests
** Select a testing area. Mozilla QA can push recommended areas to users to test around new code/features.
** Run a test, select a result, next test is shown
** Positive feedback to users: you've run this many tests, top testers of the week, etc...
* Community aspects
** Joga-style notification of special testing events, linking directly to the relevant set of tests and IRC
** Links to QMO resources that encourage people to get involved in other QA areas: bug days, bugzilla triage, etc...

= Other ideas =
* Direct link into IRC to bring testers into #qa/#testday
* David Hamp, a student at Seneca, was working on a Litmus extension but apparently didn't have much time to devote to the project during the past school year. Zach emailed him to determine what he's done and whether he's interested in working more on this. Reply: seems like he's extremely busy right now, but interested in the long-term.
* Branch/build detection to encourage testers to use current builds and to test RCs before releases. Target tests and messages to branch and trunk users.
* Need standard Big Warnings about using development software. Automatic profile backup? Need docs on how to manage having multiple versions installed and such.
* Other tabs/buttons to hook into QMO

= Naming =
* QMO Extension? Integrate the QMO branding
* Tie this in with the Mozilla beta program concept somehow?
* Hermes - Notification server
* Need a Greek name for the extension ;-)

= Content pulled from external urls =
* QMO
** Upcoming Events feed - [http://quality.mozilla.org/event/2007/06/21/feed/all/all/ the event feed]
** Recent forum posts feed - Pulled from an [http://quality.mozilla.org/extension/forum_topics rss feed] generated from a [http://quality.mozilla.org/admin/build/views/edit/9 custom view] that pulls the 10 most recent forum topics by creation date
** The latest from QMO - Generated from the top post in the [http://quality.mozilla.org/rss.xml main RSS feed]
** How you can help! - Pulled from an [http://quality.mozilla.org/extension/howtohelp_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/howtohelp this QMO page]
* Bugzilla
** Currently, the Bugzilla tab displays an [http://quality.mozilla.org/extension/bugzillatab_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/bugzillatab this QMO page]
* Litmus
** extension.cgi and json.cgi (now landed in CVS)
* Notifications
** Served by Hermes, accessed through http://litmus.mozilla.org/hermes/1/ (currently just a static xml document). The key directory on the litmus server is /opt/webtools/hermes

Litmus:Extension

2007-07-16T23:21:50Z

Zachlipton: /* Content pulled from external urls */

WeeklyUpdates/2007-07-16

2007-07-16T20:03:44Z

Zachlipton: /* QA */

[[WeeklyUpdates/2007-07-09| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2007-07-23|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 4, 2007)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* join irc.mozilla.org #staffmeeting for attendance taking and backchannel

'''note:''' all participants are muted automatically; if you want to talk, press *1 to un-mute yourself

= In Attendance =

= Development Updates =

== Fx/TB 1.5.0.13/2.0.0.5 ==
* Due a critical security bug (cross browser scripting) Fx/Tb2005 has become a firedrill release.
* A regression was found in Fx2005rc1 builds which caused a respin.
* Fx2005rc2 testing is in progress. We will have updates ready to test this evening.
* At this point the tentative release date is next Thursday (7/19), but we might be able to accelerate the release, as Fx2005 buils are ready/tested. This is to be discussed.
* Tb2005 will either be released at the same time or shortly after Fx.

== TB 3 ==
* No Announcements this week. Work continues on leak fixes, frozen linkage and hunspell integration.

== Gecko 1.9 ==

* Christian Biesinger in Mountain View
* Mac team is in town this week

== Firefox 3 ==

* Places team focused on UI ([http://wiki.mozilla.org/Places:Fx3UIPlan details])
* Download manager spec complete
* Ongoing design discussions in d-a-f
* AddOns specs in progress, Madhava and Rob Strong leading that work
* More plans to be posted this week about visual refresh
* M7 freeze next week, m8 is feature frozen (Sept 5th freeze)

== IT ==
* Build vmware migrations
* Breakpad support
* Supporting performance push and graph server enhancments

== Build ==
* VMware Migrations are completed. We're still addressing performance issues, though (tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=386074 bug 386074]). At this time, we don't think we'll have to take any substiantial downtime again, though.
* Related to that, we're aware that trunk cycle times need some work. We're discussing now how to best address this. Sub-30 minute cycle times is a requirement, and we're shooting for sub-20 minute cycles.
* The new Linux reference platform (fxnewref-linux-tbox) became the official Linux nightly build machine last week. This machine is based on the [[Linux/Runtime_Requirements]]. Thus far, we've not had any feedback regarding problems. [https://bugzilla.mozilla.org/show_bug.cgi?id=387167 Bug 387167] tracks renaming this Tinderbox after its shakedown cruise is finished.
* We're working on refreshing the Win32 reference platform as well. This is tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=384624 Bug 384624]. Please comment there if you want any additional tools added to the refresh list. We're planning on switching Win32 nightlies later this week or early next week, depending on how testing goes.
* The Build Team will be doing our bi-weekly bug triage tomorrow, 17 July.

== QA ==
Test Execution
* Firefox 2.0.0.5- Bug fix verification, smoke testing, BFT'ing, urgent testing over the weekend. See [[Firefox:2.0.0.5:Test_Plan|Test Plan]]. [juan, tomcat, abillings, marcia, tracy, others]
* Firefox 3 - [[MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:Fx3_QA_Daily_Smoketest#Major_Bugs_Discovered_during_smoketesting|Daily smoke testing]] [many]. Bug verification for Places [billing]. Test planning, and development, and testing in many areas.

Test Development
* JavaScript: Improved regression and fix detection for the JavaScript tests. Added new tests and filed a regression that was detected by the scripts! [bc]
* First draft of the [[http://wiki.mozilla.org/MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:MacOSIntegration|Firefox 3 Mac OS Test Plan]] was sent out for review [marcia]

Tools and Infrastructure

* [http://quality.mozilla.org/projects/automation/talos Talos Performance framework]:
** created script to format manifests for baseline testing [alice]
** Completed initial version of port to Mac OS (awaiting review) [zach]
** Worked out a steps to get us to a modularized framework enabling simple integration of new tests into Talos [alice]
* QA Assurance Environments: Generated and reviewed several profiles (use the same user, password as for this status report) for 1.8.1, 1.9.0 on Windows XP, Linux, Mac PPC after spidering the top 33 sites. Note the "bookmarks" profiles added each visited page to the bookmarks. Investigated location of cache and history data in trunk builds (sqllite) in order to help with profile creation for trunk builds. [bc, marcia]

== Security ==

== Marketing/PR ==
- [http://wiki.mozilla.org/Support:Alpha_Article_Tracking Support knowledge base article tracking list is live.] Need your help creating content starting this Thursday! 
- Retention plan overview and feedback session this Thursday at 3pm. 
- OSCON:
*Please help get the word out for [http://wiki.mozilla.org/Conferences:oscon07/ office hours] and our [http://www.spreadfirefox.com/node/27794/ community party]
*4 passes available for Tuesday's Radar Briefing
*See SpreadFirefox for complete lineup of [http://www.spreadfirefox.com/node/27794/ activities]

== Community ==
* Finalized top-level goals for Q3. Will share shortly. Major focus on more consistent reporting.
* Air Mozilla went great. About 150 video viewers and scores of questions coming from IRC, Email, and IM.
** Air Mozilla on demand (podcasts) to be posted in multiple formats this week.
** Interviews on Air Mozilla to become a regular feature (starting monthly, and hopefully moving to every two weeks.) Collecting suggestions for next guest. Email Asa.
* Community Connections (name subject to change) tool requirements being developed. Tool to provide what owners.html does for code for the broader Mozilla project.

== Mozilla Labs ==

== Developer Relations ==

* Built a JavaScript speed test suite to analyze Spidermonkey, Tamarin, and Rhino. (jresig)

== Webdev, Add-ons, AMO ==
* Kubla
** Alex has been making great progress here: workflow is setup, language handling is setup
* AMO
** Progress on mocks, had a good meeting last week about finalizing search/display/browse pages.
** Download count script is behind but we made progress last week. Looking to avoid dupes and get better stats for users.
* Breakpad
** Worked on bugzilla integration, among other things
* Mozilla Support
** Working with TikiWiki community on support-stage setup

= Foundation Updates =

Note that Frank is on vacation and won't be participating in the weekly call.

* Grants and related activities
** Frank completed paperwork for one more project left over from the Summer of Code applications, a project by Jörg Dotzki to create a Firefox extension to simulate the appearance of web pages to colorblind individuals.
** Frank published a blog post on a proposed accessibility vision and strategy for the Mozilla Foundation.

* IP/legal issues
** Frank formally submitted the application for US trademark registration of the Camino logo.

* Other
** Zak has been working to help get the Internet as a Public Good symposium organized.
** David has been working on various tasks related to donations to the Mozilla Foundation.
** Gerv was on holiday last week.

For more information see the individual status reports from [http://davidwboswell.wordpress.com/ David], [http://hecker.org/mozilla/foundation-activities-2007-07-13 Frank], [http://weblogs.mozillazine.org/gerv/archives/2007/07/weekly_status_20070713.html Gerv], and [http://zak.greant.com/mofo-weekly-report-2007-07-13/ Zak].

= Roundtable =

= Other Business =

ReferencePlatforms/Test/Mac

2007-07-11T18:02:33Z

Zachlipton:

=qm-pmac01-04=
Setup notes for the performance testing mac minis (Talos boxes)

Syck 0.55 is installed on pmac01 for Talos. Should be installed on the other machines. Installed the main binary and the python extension:

* cd ext/python/
* python setup.py build
* sudo python setup.py install

pmac01 also has xcode and ports installed from the reference machine. Sharedmenuframeworks is not installed. Screensaver disabled.

For Talos to work on mac, the Subprocess module must be installed. Download subprocess.py from [https://intranet.mozilla.org/images/2/20/Subprocess.py] and copy into /Library/Python/2.3/site-packages/. Be sure to save the file as 'subprocess.py' with a lowercase 's'.

ReferencePlatforms

2007-07-11T18:02:15Z

Zachlipton: /* Test Reference Platforms */

= Build Reference Platforms =

* [[ReferencePlatforms/Win32|Win32]]
* [[ReferencePlatforms/Mac|MacOSX]]
* [[ReferencePlatforms/Linux|Linux-CentOS 4.4]]
* [[ReferencePlatforms/Linux-CentOS-5.0|Linux-CentOS 5.0]]
* [[ReferencePlatforms/BuildBot|BuildBot]]
** [[ReferencePlatforms/BuildBot/Win32|Win32]]
** [[ReferencePlatforms/BuildBot/MacOSX|MacOSX]]
** [[ReferencePlatforms/BuildBot/Linux|Linux]]

= Test Reference Platforms =

* [[ReferencePlatforms/Test/WinXP|WinXP]]
* [[ReferencePlatforms/Test/Mac|Mac]]
* [[ReferencePlatforms/Test/WinXP (Tinderbox)|WinXP (Tinderbox)]]
* [[ReferencePlatforms/Test/Linux FC4 (Tinderbox)|Linux FC4 (Tinderbox)]]
* [[ReferencePlatforms/Test/Linux FC6 (Tinderbox)|Linux FC6 (Tinderbox)]]

ReferencePlatforms/Mac

2007-07-11T18:01:57Z

Zachlipton: /* qm-pmac01-04 */

__TOC__

= Darwin Version =

These are the kernel versions we're starting with:

PPC: Darwin xserve03.build.mozilla.org 8.7.2 Darwin Kernel Version 8.7.2: Tue Jul 25
23:14:47 PDT 2006; root:xnu-792.10.96.obj~3/RELEASE_PPC Power Macintosh powerpc

Intel: Darwin bm-xserve08.build.mozilla.org 8.8.4 Darwin Kernel Version 8.8.4: Sun Oct 29 15:26:54 PST 2006; root:xnu-792.16.4.obj~1/RELEASE_I386 i386 i386

= Initial Setup and Account Creation =

# Change the resolution to 1024 x 768, 60 Hz, under System Preferences->Displays.
# Change the password for the administrator user to the standard build system root password.
# Create a new admin-equiv account for the cltbld user using the standard build password.
# Under System Preferences->Sharing->Apple Remote Desktop->Access Privileges change the VNc screen control password to the standard build password. NOTE: your VNC session will drop when you do this. You'll need to reconnect with the new password.
# If the hostname is wrong, e.g. unused-*, use <code>sudo scutil --set HostName new.hostname.mozilla.org</code> to fix it. NOTE: you'll need to restart the machine for this to fully take effect.
# Under System Preferences->Software Update, turn off automatic update checking.
# Using the Workgroup Manager, open the Preferences pane for the cltbld user. Under Software Update, set Manage: to Always, and set the Software Update server to use: as http://bm-xserve01.build.mozilla.org:8088/

= ssh =
The first step is to get ssh working with the cltbld keys on the new machine. Unfortunately, this presents a bit of a chicken-and-egg problem, as the ssh keys necessary to access cvs are not yet on the machine.

Two possible solutions are:

# checkout the cltbld ssh keys on a machine that already has the keys installed and then scp the .ssh directory over (<code>ocvs -d :ext:cltbld@cvs.mozilla.org:/mofo co -d .ssh release/tinderbox-configs/host/ssh; scp -r .ssh new_machine:~</code>)
# scp the cltbld keys over directly from a machine that already has them installed (<code>cd ~;scp -r xserve06:~/.ssh .</code>)

= ENV setup =

ocvs -d :ext:cltbld@cvs.mozilla.org:/mofo co release/tinderbox-configs/host
ln -s release/tinderbox-configs/host/mac-osx-profile .profile

...at which point you'll probably want to restart your shell to use the new .profile.

= Ref platform packages =

The next step is to retrieve the Mac reference platform packages from CVS:

ocvs -d :ext:cltbld@cvs.mozilla.org:/mofo co ref-platforms/mac

This should yield 4 files:

e6d9176e0b56a4dfaff7aa6e98335a88 DarwinPorts-1.3.1-10.4.dmg
65c3aeb974f5f8c75b8daa92c9185122 SharedMenusCocoa.dmg
039b8961863bd240817a6eed38f67704 dports.tar.gz
1d89f956ea2ee3a248449c3c0e0d6834 xcode_2.2.1_8g1165_018213632.dmg

= Installing Xcode =

# Mount the Xcode disk image, and begin installing the XcodeTools.mpkg.
# When it comes time to choose the '''Installation Type''', choose "Customize"
# Under "Cross-Development," select all the available SDKs, and then click "Install"

= Installing DarwinPorts =

* Install the DarwinPorts package.
* Unpack the dport tarball of packages and move them into place:

cd ~ref-platforms/mac
tar zxf dports.tar.gz
cd /opt/local/var
mv db db.old
mkdir db
mv ~/ref-platforms/mac/dports.MozillaReferencePlatform db/
cd db/
ln -s dports.MozillaReferencePlatform dports

* Next, you need to install a series of ports, all of which should already be contained (and the right version) in the dports tarball you just unpacked. If you see the port command hitting the network at all while installing the needed ports, something has gone wrong. Here is a short script that will install all the needed ports. Some of the ports have dependencies, so installing them in a different order would probably cut down on time, but I'm just listing them all here alphabetically for clarity:

#!/bin/bash
port -f install apr @1.2.7_0
port -f install apr-util @1.2.7_0
port -f install cvs @1.11.21_0
port -f install db4 @4.3.29_0
port -f install expat @2.0.0_1
port -f install gettext @0.14.6_0
port -f install glib2 @2.10.3_0
port -f install libiconv @1.10_1
port -f install libidl @0.8.6_0
port -f install neon @0.25.5_0
port -f install openssl @0.9.8b_0
port -f install pkgconfig @0.20_0
port -f install subversion @1.3.2_0
port -f install wget @1.10.2_0
port -f install zlib @1.2.3_0

Running <code>port installed</code> after you're done should show only the 15 ports listed above as installed.

= Installing SharedMenusCocoa =

# Open the SharedMenusCocoa image.
# Copy the SharedMenusCocoa.framework directory from SharedMenusCocoa/build to /Library/Frameworks
# Follow [http://wiki.caminobrowser.org/Development:Building the instructions on the Camino build reference page] for creating the links in the older SDKs. If you are building on an Intel Mac or need to build a Universal Camino, you will also need to follow the instructions for recompiling a UB version of the framework. NOTE: make sure you have the SharedMenusCocoa.framework linked under ALL your SDKs (including 10.4) just to be safe.

= chown scripts =

After you've created your initial /builds/tinderbox directory structure, checkout and build the following tools that are also required for changing permissions while packaging on Macs:

cd ~
cvs -d :ext:cltbld@cvs.mozilla.org:/cvsroot co mozilla/build/macosx/permissions
cd mozilla/build/macosx/permissions
gcc -o chown_revert chown_revert.c
gcc -o chown_root chown_root.c
mkdir -p /builds/tinderbox/bin
cp chown_revert chown_root /builds/tinderbox/bin
cd /builds/tinderbox/bin
chmod 4755 chown*
sudo chown root chown*
ln -s chown_revert revert_root

= Establish initial ssh connections and accept keys =

You'll need to execute the following simple ssh calls to connect to the ftp server (stage), symbol server, and update server so that the various pieces of the build can be uploaded automatically by the build scripts when needed:

ssh stage.mozilla.org pwd
ssh -2 -f -L2222:hal:22 stage.mozilla.org sleep 20;ssh -2 -p2222 -l symbols localhost pwd
ssh -i /Users/cltbld/.ssh/aus cltbld@aus2-staging.mozilla.org pwd

= Mail config =

You'll need to update the postfix config to make sure that <code>myhostname</code> is set correctly and that large messages can be sent. The tail of <code>/etc/postfix/main.cf</code> should look similar to:

myhostname = bm-xserve08.build.mozilla.org
mailbox_transport = cyrus

# Allow large messages (unlimited size, required for tinderbox)
message_size_limit = 0

You'll then want to restart postfix to pick up the changes.

ReferencePlatforms/Mac

2007-07-03T19:05:25Z

Zachlipton: /* qm-pmac01-04 */

ReferencePlatforms/Mac

2007-07-03T17:09:50Z

Zachlipton: /* qm-pmac01-04 */

Litmus:Extension/Notification

2007-06-29T02:47:11Z

Zachlipton: /* Notification classes and types */

= Overview =
One of the QA Extension's major features is the ability to send notifications to users for testdays, bugdays, pre-release testing, qa news, special announcements, and other things we want to bring to the attention of our testing community. These notifications are displayed in a small notification box in the user's browser, similar to the way the Joga Companion displayed soccer match notifications. By default, few notifications will be enabled, but users may set their notification preferences from the settings tab.

= Architecture =
Hermes is the name of the notification server: a small web application that aggregates notification sources and generates an xml document to be sent to clients on request. This xml document contains all notifications from the last 10 days. From time to time (every 90 minutes currently), the client requests the notification document, converts the xml into Notification javascript objects, and stores the notifications in a mozstorage (sqlite) database.

The database is then read for any undisplayed notifications, and only one notification will be displayed each 90 minutes, with a maximum of two each day (except for news if the user has turned this setting on). Older notifications will be skipped as needed.

== Dates and Times ==
All timestamps shall be in ISO 8601 form -- 'YYYY-MM-DDThh:mm:ssZ' -- or with a [+-]HH:MM time zone designation, as understood by [http://mochikit.com/doc/html/MochiKit/DateTime.html#fn-isotimestamp MochiKit.DateTime].

== Notification classes and types ==
Each notification has a class ('event' or 'announce') and a type:

* 'event' class
** testday
** bugday
** special
* 'announce' class
** news
** prerelease
** newbuilds
** special

These types correspond to user settings to enable and disable various types of notifications.

== Notification Display ==
Notifications will be displayed according to user preferences and the following rules:
* Events -
** eventAdvanceNotificationDays in advance of the event (5 days?)
** When the event is begining
* Announcements -
** When a previously unseen notification id is received

== Security ==
Does https need to be used? The extension obviously runs with chrome privs, so a malicious notification document could be used to compromise the browser unless sanitized properly by the client.

= Example notification document =
<pre>
<notifications>
<notification
class="event"
type="testday"
id="3ad65570-bd22-4add-8e99-c7c329f84b19"> [can also be numeric, doesn't matter as long as it's unique]
<headline>Firefox Alpha 6 Testday</headline>
<eventinfo> [for class="event"]
<datetime>2007-06-28T17:44:06Z</datetime>
<place>irc.mozilla.org, #testday</place> [optional]
</eventinfo>
<infotext>Come join us for the...</infotext>
<infolink href="http://example.com">Click here to learn more</infolink>
<golink href="http://example.com/2">Click here to get started now</golink>
</notification>
[more notifications as needed...]
</notifications>
</pre>

2007-06-26T23:20:17Z

Zachlipton: /* Other ideas */

Litmus:Extension

2007-06-26T23:07:43Z

Zachlipton: /* Content pulled from external urls */

= Goals =
* Make it easier for new testers to get started
* Allow testers to view tests and submit results from a separate window inside the app
* Make testers feel valued and encourage them to keep testing
* Help integrate testers into the community
* Encourage participation in special events (testdays, pre-release testing, etc...)

= Feature Areas =
* Initial setup
** Helps users get setup with an account if they don't already have a Litmus account. Provides an introduction to Mozilla QA, what we do, how testing works.
** One guided process from installing the extension to submitting their first test result, real easy and welcoming
* Running tests
** Select a testing area. Mozilla QA can push recommended areas to users to test around new code/features.
** Run a test, select a result, next test is shown
** Positive feedback to users: you've run this many tests, top testers of the week, etc...
* Community aspects
** Joga-style notification of special testing events, linking directly to the relevant set of tests and IRC
** Links to QMO resources that encourage people to get involved in other QA areas: bug days, bugzilla triage, etc...

= Other ideas =
* Direct link into IRC to bring testers into #qa/#testday
* David Hamp, a student at Seneca, was working on a Litmus extension but didn't have much time to devote to the project during the past school year. Zach emailed him to determine what he's done and whether he's interested in working more on this. It seems as though he's extremely right now, but seems interested in the long-term.
* Branch/build detection to encourage testers to use current builds and to test RCs before releases. Target tests and messages to branch and trunk users.
* Need standard Big Warnings about using development software. Automatic profile backup? Need docs on how to manage having multiple versions installed and such.
* Other tabs/buttons to hook into QMO

= Naming =
* QMO Extension? Somehow integrate the QMO branding
* Tie this in with the Mozilla beta program concept somehow?

= Questions =
* Extension presents a separate interface to Litmus different than that of the website. Is this a problem?
* Just Firefox, or allow Thunderbird/calendar/etc... testing through the extension?

= Content pulled from external urls =
* QMO
** Upcoming Events feed - [http://quality.mozilla.org/event/2007/06/21/feed/all/all/ the event feed]
** Recent forum posts feed - Pulled from an [http://quality.mozilla.org/extension/forum_topics rss feed] generated from a [http://quality.mozilla.org/admin/build/views/edit/9 custom view] that pulls the 10 most recent forum topics by creation date
** The latest from QMO - Generated from the top post in the [http://quality.mozilla.org/rss.xml main RSS feed]
** How you can help! - Pulled from an [http://quality.mozilla.org/extension/howtohelp_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/howtohelp this QMO page]
* Bugzilla
** Currently, the Bugzilla tab displays an [http://quality.mozilla.org/extension/bugzillatab_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/bugzillatab this QMO page]

Litmus:Todo

2007-06-26T23:01:15Z

Zachlipton: /* Zach Lipton */

'''[[Litmus|« back to Litmus main page]]'''

= Litmus To-Do List =

Here's some things that Litmus needs. If you feel like taking one of these tasks on, great! Just post about your progress on this page.

* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Open Litmus Bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Assigned Litmus Bugs]

== Unclaimed Tasks ==

* '''Attachments''': do we still have a need for attachments? We're not trying to replace Bugzilla here, and there's a pretty high potential for abuse. We might want to allow this for community proposals for changes to test cases.

* '''Bugzilla Bug Integration''': automatically mark-up bugs numbers in comments and test steps/expected results as links to Bugzilla.

* '''Log File Support''': Build UI for display of result logs, which will now be held in the database to facilitate comparison.

* '''Test result/run comparison''': we need to be able to compare single test results head-to-head, and we also need to display comparisons between entire test runs. We can take a page from LXR's book and mark up the deltas in special colors to facilitate comparisons. We might also want to use some AJAX to roll-up the parts of the comparison that are the same.

* '''Backup/Archive/Purging of old test results''': the first step here will be to determine what our data retention policy will be. Both Bob and Tracy have said that they never need to go back further than one month to compare test results, but their opinions might change if it were easier for them to do so. It might make sense to be able to tag particular test runs, e.g. test runs for releases, with a DO_NOT_PURGE flag so that they can be kept around indefinitely;

== Claimed Tasks ==

=== Chris Cooper ===
* In Progress
** {{bug|355298}}: Need strawman data for new installs
** {{bug|360620}}: Unable to revoke admin status, DB sessions not revoked
** [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=ccooper%40deadsquid.com&emailassigned_to2=1 Bugs currently assigned to coop]

* Completed Tasks
** '''Test Runs''': this is the major piece that is present in Testrunner but still missing in Litmus. Design is listed in [[Litmus:Design#Replicate_Testrunner_Functionality]].
** '''Updated reporting tools''': since these tools need to know about test runs anyway, I'm taking this opportunity to update them as well.
** '''Administration Interface'''
** '''Testcase/Subgroup/Testgroup Management'''
** add "Search for testcase" functionality -> search by: testgroup, subgroup, product
** added full-text search (by summary, steps, expected results)
** database re-architect for test runs;
** add group listing (i.e. this testcase belongs to the following groups)
** only display testcases that are not marked as obsolete to regular testers. Admin can see all testcases.
** script to grab/update test cases from Testrunner
*** add Testrunner ID and version fields to Litmus tests table
** get litmus mailing alias setup
*** we're going to tag along on the existing dev-apps-webtools@lists.mozilla.org mailing list
** '''Litmus Roadmap'''
*** milestones + dates for version 1.0 and beyond
** '''Reporting/Querying'''
** '''New Schema'''
** '''UI Improvement'''
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=302688 bug 302688]
** '''Multiple comments and bug numbers per test result'''
** '''Migration of New Firefox 1.5 BFTs from Testrunner to Litmus'''
** '''General Litmus cleanup prior to community testing debut of Litmus'''
*** no results text for statistics
*** improve front page UI: login box, make results display less wide, interim logout functionality
*** comment icons à la tinderbox
** fix the percentage system used for running tests
*** make percentages based on build ID, rather than time
*** display community coverage percentages as well as personal percentages

=== Zach Lipton ===

* In Progress
** QMO Extension
[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=zach%40zachlipton.com&emailassigned_to2=1 Bugs currently assigned to zach]

* Completed Projects
** '''User info''': personal pages for testers where they can change their information.
** '''The testdata filter'''
*** The testdata filter (in Template.pm) is in pretty bad shape and needs to get fixed. It likely opens us up to XSS attacks if we actually had a real cookie to attack. [[User:Zachlipton|Zachlipton]] 11:03, 28 Jul 2005 (PDT)
** '''litmusconfig.js'''
*** Select boxes need to be converted to pull data from litmusconfig.js rather than the clunky show/hide div approach. [[User:Zachlipton|Zachlipton]] 15:47, 29 Jul 2005 (PDT)
** '''Precompiled templates'''
** '''Authentication''': there is currently no authentication in Litmus. We accept the first email address the user provides when testing, use this to build a cookie, and then never let them change it (without removing the cookie, of course). We need to implement proper authentication:
*** '''Status''': Initial version checked into CVS 1/7/06. Working on migration to allow user accounts from the previous system to be used under the new authentication system.
** '''Update Documentation'''
*** How to checkout Litmus from CVS doc on wiki
*** Update README
*** Update INSTALL
*** Update auth information on wiki and add API description
** '''User management''': admin tools for working with user accounts;
** '''Web Services Interface - Design'''
*** Need to have a XML-RPC whatever interface to Litmus to get tests, submit results, etc...

Litmus:Extension

2007-06-22T17:29:52Z

Zachlipton: /* Content pulled from external urls */

= Goals =
* Make it easier for new testers to get started
* Allow testers to view tests and submit results from a separate window inside the app
* Make testers feel valued and encourage them to keep testing
* Help integrate testers into the community
* Encourage participation in special events (testdays, pre-release testing, etc...)

= Feature Areas =
* Initial setup
** Helps users get setup with an account if they don't already have a Litmus account. Provides an introduction to Mozilla QA, what we do, how testing works.
** One guided process from installing the extension to submitting their first test result, real easy and welcoming
* Running tests
** Select a testing area. Mozilla QA can push recommended areas to users to test around new code/features.
** Run a test, select a result, next test is shown
** Positive feedback to users: you've run this many tests, top testers of the week, etc...
* Community aspects
** Joga-style notification of special testing events, linking directly to the relevant set of tests and IRC
** Links to QMO resources that encourage people to get involved in other QA areas: bug days, bugzilla triage, etc...

= Other ideas =
* Direct link into IRC to bring testers into #qa/#testday
* David Hamp, a student at Seneca, was working on a Litmus extension but didn't have much time to devote to the project during the past school year. Zach emailed him to determine what he's done and whether he's interested in working more on this. It seems as though he's extremely right now, but seems interested in the long-term.
* Branch/build detection to encourage testers to use current builds and to test RCs before releases. Target tests and messages to branch and trunk users.
* Need standard Big Warnings about using development software. Automatic profile backup? Need docs on how to manage having multiple versions installed and such.
* Other tabs/buttons to hook into QMO

= Naming =
* QMO Extension? Somehow integrate the QMO branding
* Tie this in with the Mozilla beta program concept somehow?

= Questions =
* Extension presents a separate interface to Litmus different than that of the website. Is this a problem?
* Just Firefox, or allow Thunderbird/calendar/etc... testing through the extension?

= Content pulled from external urls =
* QMO
** Upcoming Events feed - [http://quality.mozilla.org/event/2007/06/21/feed/all/all/ the event feed]
** Recent forum posts feed - Pulled from an [http://quality.mozilla.org/extension/forum_topics rss feed] generated from a [http://quality.mozilla.org/admin/build/views/edit/9 custom view] that pulls the 10 most recent forum topics by creation date
** The latest from QMO - Generated from the top post in the [http://quality.mozilla.org/rss.xml main RSS feed]
** How you can help! - Pulled from an [http://quality.mozilla.org/extension/howtohelp_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/howtohelp this QMO page]