SeaMonkey/StatusMeetings/2012-10-16: Difference between revisions

← Older edit

SeaMonkey/StatusMeetings/2012-10-16 (view source)

Revision as of 13:17, 16 October 2012

771 bytes added , 16 October 2012

→‎Any other business?

Philip Chee

Confirmed users

2,595

edits

@@ Line 33: / Line 33: @@
 *** sea-master1 will replace the current buildmaster.
 ** {{Bug|740633}} set up seamonkey HPs in scl3. Hardware installed and iLO configured. CentOS 6.3 installed. sea-puppet is online. Callek to set the host up as a puppet master.
-* Linux builds have been failing because the GTK version installed on the tinderboxen was too told. See {{Bug|795354}} on updating the GTK version on the tinderboxen. {{Bug|794285}} has lowered the GTK version requirement back to 2.10 for now (also see {{Bug|793634}} on this, in the future GTK 2.18 and glib 2.22 will be required).
+* Linux builds have been failing because the GTK version installed on the tinderboxen was too old. See {{Bug|795354}} on updating the GTK version on the tinderboxen. {{Bug|794285}} has lowered the GTK version requirement back to 2.10 for now (also see {{Bug|793634}} on this, in the future GTK 2.18 and glib 2.22 will be required).
 * Linux 64bit builds are failing ({{Bug|798921}}) since mozilla-central {{Bug|797671}} landed.
 ** This is due to us having an older binutils package on the machine 2.17.50.0.6-2.
@@ Line 43: / Line 43: @@
 ** {{Bug|776426}} Set up ccache on all MacOSX systems. CCACHE is installed on the MacOSX systems. Buildbot config changes to enable ccache usage have been checked in. Currently waiting to see if this fix sticks.
 ** {{Bug|791442}} Mac trunk build with clang and XCode 4.1 failing. Callek is investigating. Current solution will be to install Mac OS X 10.7 (already done) and all required software on the sea-mini-osx64-1..4 and do buildbot magic to only build on the new macs and test on our "old" ones. There is no solution yet for the machines cb-sea-miniosx64-01..3.
+* Localized SeaMonkey central & aurora Linux & Mac builds busted. A fix is in progress in {{Bug|799626}}.
 === Release Train ===
+It's been busy two weeks again with 3 releases including a chemspill. And another one potentially coming up, which would further delay 2.14b1. The benefit would be that the Addressbook fix could ride along.
 * 2.13b6 shipped October 5
 * 2.13 shipped October 9
@@ Line 63: / Line 65: @@
 ** We now have a webpage for latest builds available for "Legacy Platforms" like PPC ({{Bug|759315}}) but hikerbiker suggests making the Legacy/PPC link more discoverable ([http://forums.mozillazine.org/viewtopic.php?p=12254183#p12254183 Mozillazine post]). IanN agrees that the current link is not easily found. InvisibleSmiley said that he didn't want it to be too obvious or highlighted. IanN thinks splitting and renaming Old to Previous isn't a bad idea and moving Unofficial Releases after it. Perhaps merging Contributed builds into it.
 *** This is now {{Bug|788543}} SeaMonkey - PPC Legacy links are not easy to find.
-*** IanN to check with InvisibleSmiley what he wants to do about this.
+*** The point is that the new page lists external projects, i.e. projects we have no control over and where we cannot estimate the level of quality, provide no support etc. InvisibleSmiley really dislikes the idea of exposing any of that more than necessarily. So, if someone puts up a viable suggestion on the corresponding bug and people (read: seamonkey-members) agree that's what should be done, Jens will do it, otherwise not.
 * See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
@@ Line 72: / Line 74: @@
 [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&resolution=FIXED&field0-0-0=target_milestone&field0-1-0=cf_status_seamonkey213&field0-2-0=target_milestone&field0-3-0=cf_status_seamonkey212&field0-4-0=cf_status_seamonkey211&field0-5-0=cf_status_seamonkey210&field0-6-0=cf_status_seamonkey29&field0-7-0=cf_status_seamonkey28&field0-8-0=cf_status_seamonkey27&field0-9-0=cf_status_seamonkey26&field0-10-0=cf_status_seamonkey25&field0-11-0=cf_status_seamonkey24&field0-12-0=cf_status_seamonkey23&field0-13-0=cf_status_seamonkey22&field0-14-0=cf_status_seamonkey21&type0-0-0=regexp&type0-1-0=equals&type0-2-0=notregexp&type0-3-0=notsubstring&type0-4-0=notsubstring&type0-5-0=notsubstring&type0-6-0=notsubstring&type0-7-0=notsubstring&type0-8-0=notsubstring&type0-9-0=notsubstring&type0-10-0=notsubstring&type0-11-0=notsubstring&type0-12-0=notsubstring&type0-13-0=notsubstring&type0-14-0=notsubstring&value0-0-0=^(seamonkey2.13|seamonkey2.14|seamonkey2.15)$&value0-1-0=fixed&value0-2-0=^(seamonkey2.12|seamonkey2.11|seamonkey2.10|seamonkey2.9|seamonkey2.8|seamonkey2.7|seamonkey2.6|seamonkey2.5|seamonkey2.4|seamonkey2.3|seamonkey2.2|seamonkey2.1|seamonkey2.0)$&value0-3-0=fixed&value0-4-0=fixed&value0-5-0=fixed&value0-6-0=fixed&value0-7-0=fixed&value0-8-0=fixed&value0-9-0=fixed&value0-10-0=fixed&value0-11-0=fixed&value0-12-0=fixed&value0-13-0=fixed&value0-14-0=fixed fixed] (6)
+* We've had one chemspill (2.13.1) with potentially another one coming up.
 * One tracked 2.5 issue still open.
-** 2.1 through 2.7 have NOT included the ka (Kartvelian aka Georgian) locale. The last release with ka locale shipped was 2.0.14. The ka l10n maintainer has made some recent updates but.
+** 2.1 through 2.7 have NOT included the ka (Kartvelian aka Georgian) locale. The last release with ka locale shipped was 2.0.14. The ka l10n maintainer has made some recent updates but;
-** Callek needs to look into whether to remove |ka| from our [current] automation entirely or if ka can be sustained going forward. Tracked in {{bug|667147}}. ''[Needs update from Callek]''.
+** Callek thinks we should remove ka, unless we can get commitment from the ka person to actually update things himself instead of dumping tarballs on us and expecting us to check it in for him. Tracked in {{bug|667147}}.
 * [http://www.seamonkey-project.org/releases/seamonkey2.13/ SeaMonkey 2.13 Release Notes]
 * [http://www.seamonkey-project.org/releases/seamonkey2.13/changes#fixes2131 Fixes in 2.13.1]
@@ Line 255: / Line 258: @@
 ==== Ratty ====
 Fixed:
-* {{Bug|789954}} TEST-UNEXPECTED-FAIL <tt>| /tests/suite/browser/test/test_contextmenu.html |</tt> Test timed out. (Port Port {{Bug|778420}} Fix up tests that don't like the new enablePrivilege). Mostly fixed, waiting for post landing reviews.
+* {{Bug|789954}} TEST-UNEXPECTED-FAIL <tt>| /tests/suite/browser/test/test_contextmenu.html |</tt> Test timed out. (Port Port {{Bug|778420}} Fix up tests that don't like the new enablePrivilege). Fixed, but leaving open for post landing reviews.
 * {{Bug|799131}} Update calls to saveURL() etc. due to function signature change in {{Bug|795065}} (Add privacy status to nsDownload).
 * {{Bug|800197}} Warning Popup for Failed Find Has Wrong Title Bar.
@@ Line 283: / Line 286: @@
 === Any other business?  ===
-* '''Geolocation'''
+* '''Bug Day''':
-** Geolocation now works out of the box. MoCo turned it on by default for all applications that build off mozilla-central. However we're not even sure we are legally allowed to ship with the URL in, we might need to actually put in a pref to disable that in newer builds.
+** Useful link: [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=], also see [https://wiki.mozilla.org/SeaMonkey/Bug_events/20120921#Results] for results.
-** No news to date. Callek will have to reach out to his MoCo legal contact again ''Real Soon Now''.
+** Tallying Bug Day results: still in progress. See Tonymec's roundtable entry for details.
 * '''Test failures'''
 ** <u>qawanted</u>, especially on Linux and MacOSX specific issues: reproducing and reporting would already help.
 ** Serge says that on Linux and MacOSX, he just needs someone to actually run the tests and report what they see (screen, console, etc). For example, there is a Mac test about Ctrl+W not working. This should be so trivial.
-** tonymec suggests that any enthusiastic user, even non-technical, should be able to do some testing (litmus?) and not be scared by technical language and such.
+** Tonymec suggests that any enthusiastic user, even non-technical, should be able to do some testing (litmus?) and not be scared by technical language and such.
 ** IanN suggests reaching out to the user community using the newsgroups and forums.
 ** Ratty to liaise with Serge when he gets back on doing a write up how the community can help us with this.