SeaMonkey/StatusMeetings/2011-11-01: Difference between revisions

Jump to navigation Jump to search
 
(33 intermediate revisions by 7 users not shown)
Line 7: Line 7:


== Agenda ==
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Who's taking minutes? -> '''Ratty'''
* Nominees for Friends of the Fish Tank?
* Nominees for Friends of the Fish Tank?
** Tony Mechelynck for organising the bug event.
** Tony Mechelynck for organising the bug event.
** Px and Mnyromyr for lots of bug triaging during the bug event.
** Px and Mnyromyr for lots of bug triaging during the bug event.
** Callek for services above and beyond the call of duty in getting builds working again.
** Callek and the Mozilla RelEng team for services above and beyond the call of duty in getting SeaMonkey builds working again.
** Please note ''A person or entity can't be nominated twice in a row''.
** Please note ''A person or entity can't be nominated twice in a row''.


Line 24: Line 24:
'''CLOSED'''
'''CLOSED'''


=== Status of Buildbot Master and Our Tree ===
=== Status of the SeaMonkey Buildbot Master and Tree ===
Previously on Buffy the Vampire Slayer:
Previously on Buffy the Vampire Slayer, Callek said:
* "What Happened?"
* "What Happened?"
** One XServe that hosts "Parallels" in Mozilla died, taking down with it all the data it housed. (There were two problems to appear here)
** One XServe that hosts "Parallels" in Mozilla died, taking down with it all the data it housed. (There were two problems to appear here)
* "What VM's does that translate to?"
* "What VM's does that translate to?"
** Parallels can only reliably (for us anyway) run 7 total VM's; Which are: 1 "Linux32 CentOS5.0 Buildbot Master", 2 "Linux32 Centos5.0 Buildbot Slaves", 1 "Linux64 Centos5.0 Buildbot Slave", 3 "Win32 w2k3 Buildbot Slaves"
** Parallels can only reliably (for us anyway) run 7 total VM's; Which are: 1 "Linux32 CentOS5.0 Buildbot Master", 2 "Linux32 Centos5.0 Buildbot Slaves", 1 "Linux64 Centos5.0 Buildbot Slave", 3 "Win32 w2k3 Buildbot Slaves"
Line 48: Line 49:
* "When can I land my patches?"
* "When can I land my patches?"
** I'll make the confirmation now, that any patches slated to land on aurora/beta and any [simple] regression fixes, and any bustage fixes, can land with explicit approval. And all must have been tested locally. Where possible also test other OS's as well. If in doubt, ask yourself if the risk of it landing with no builds is worse than the trouble the bug causes. (since at this point, I'm unsure if any beta patches will be able to have coverage before my next/final beta build)
** I'll make the confirmation now, that any patches slated to land on aurora/beta and any [simple] regression fixes, and any bustage fixes, can land with explicit approval. And all must have been tested locally. Where possible also test other OS's as well. If in doubt, ask yourself if the risk of it landing with no builds is worse than the trouble the bug causes. (since at this point, I'm unsure if any beta patches will be able to have coverage before my next/final beta build)
'''Current Situation'''
(To be updated)
* Callek has a temporary buildbot master up and running and we have been able to get some builds out. Some nightlies are available from the 30th onwards.
* We still don't have all machines up (about half of the Linux and Windows machines and the Linux64 machine are still missing), but we have some coverage on the major platforms. Windows will just take longer than usual to build due to only having 2 of 5 machines up.
* Tree is still closed unless you have tested things up, down, and sideways.
** Callek says we can open the tree to METERED.
** What's METERED? Approval required and try to not get too many pushes in short order.


=== Release Train ===
=== Release Train ===
Line 54: Line 63:
* 2.5b3 shipped 14th October.
* 2.5b3 shipped 14th October.
* Target date for 2.5 is around 8th November. (Note: This sounds unlikely given the tree closure. Update/new ETA needed.)
* Target date for 2.5 is around 8th November. (Note: This sounds unlikely given the tree closure. Update/new ETA needed.)
* We expect at least 1 more beta, perhaps two. The buildbot master being down (went down two weeks ago) may cause a delay or even make us miss one beta. buildbot down is {{Bug|695278}}). A brief chat with IT indicates it may require a colo-trip. Unfortunately only one person really knows how to administer the machine those VM's are on. (Update?)
* We expect at least 1 more beta, perhaps two. The buildbot master being down (went down two weeks ago) may cause a delay and we will probably miss one beta. buildbot down is {{Bug|695278}}). A brief chat with IT indicates it may require a colo-trip. Unfortunately only one person really knows how to administer the machine those VM's are on.
* '''Update:''' Callek is on the East Coast so he's probably been hit by storm related power cuts. We will need to discuss VM administration when Callek is back online.


=== Extensions Compatibility Tracking ===
=== Extensions Compatibility Tracking ===
Line 85: Line 95:


* The [[SeaMonkey/Features/2.4|New 2.4 Features]] page has a comprehensive list of features.
* The [[SeaMonkey/Features/2.4|New 2.4 Features]] page has a comprehensive list of features.
* 2.4.x had ~X ADU yesterday and 2.4.1 has had ~Y downloads so far.
* 2.4.x had ~80,800 ADU by last Thursday and 2.4.1 has had ~217,100 downloads so far.
** vs. A on 2.3, B on 2.2, C on 2.1 and D on 2.0. So, in the last two weeks, ~Ek have migrated to 2.3 and above.
** Of the released versions, as of last Thursday, we have 23.4% on 2.0, 1.2% on 2.1, 3.8% on 2.2, 6.4% on 2.3 and 65.1% on 2.4. So, in the last two weeks, ~6k (an additional 4.9% of ADU) have migrated to 2.4


==== 2.Next ====
==== 2.Next ====
Line 92: Line 102:
** Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.
** Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.
** Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.
** Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.
* Please help updating the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go.
* Remember to help update the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go along.


=== Feature List, Planning ===
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 36 new, 12 fixed, 102 triaged.
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 36 new, 12 fixed, 102 triaged.
* Very good triage effort over the Seamonkey Halloween Bug Event.
* Very good triage effort during the Seamonkey Halloween Bug Event.
* Good further triage targets could come out of looking at the [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=--- component bug counts], pick yours!
* Good further triage targets could come out of looking at the [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=--- component bug counts], pick yours!


Line 111: Line 121:
** Progressing slowly, still waiting on reviews from TB side. Full customization has to go to 2.next (currently 2.6 but could be pushed back further) as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.
** Progressing slowly, still waiting on reviews from TB side. Full customization has to go to 2.next (currently 2.6 but could be pushed back further) as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.
** IanN will need to poke some people about reviews not happening quickly enough.
** IanN will need to poke some people about reviews not happening quickly enough.
** IanN has done as much unpicking of Composer/Mail Compose code as possible in the dependent bugs, so will be reworking his customising patches.
** IanN is still wading through the unpicking of Composer/Mail Compose code in the dependent bugs. After that he will be reworking his customising patches.
* de-RDF {{bug|654864}} has been finished and landed on all development branches, including 2.3. Still to do:
* de-RDF {{bug|654864}} has been finished and landed on all development branches, including 2.3. Still to do:
** Neil wanted to follow up on some listener issues
** Neil wanted to follow up on some listener issues. This is being addressed in {{bug|669203}}.
** for the selection issue, see what the TB guys come up with in {{bug|669203}}
** for the selection issue, see what the TB guys come up with in {{bug|669203}}. There is still a patch that needs checking in but both the patches there are for SM (even though it is a TB bug :P).
* {{bug|477845}} Build a standalone (Comm-central) Composer. [kaze]
* {{bug|477845}} Build a standalone (Comm-central) Composer. [kaze]
** ''kaze'' has done a bit of work in this bug recently. Building on Windows works. Now supports debug builds on Linux if tests are disabled (--disable-tests). Still a lot to do.
** ''kaze'' has done a bit of work in this bug recently. Building on Windows works. Now supports debug builds on Linux if tests are disabled (--disable-tests). Still a lot to do.
Line 220: Line 230:


==== KaiRo ====
==== KaiRo ====
* Followed all the news on the main SeaMonkey VM host going down ({{bug|695278}}), helped Callek slightly with getting the SeaMonkey buildmaster up and running everything again after Mozilla IT got that one up (mainly did some debugging and fixing on clobberer).
* Also updated the community update server to current AUS2 trunk code so we can handle extended snippet data in the future.
* I did some more work on my themes and finally uploaded 2.4 versions of both [https://addons.mozilla.org/addon/earlyblue/versions/2.4 EarlyBlue] and [https://addons.mozilla.org/addon/lcarstrek/versions/2.4 LCARStrek] which are awaiting reviews now.
* Put some more work into cleanups of my Mandelbrot add-on and implemented a "Back" function in the Location menu. With that, I uploaded it as the [https://addons.mozilla.org/addon/addon/kairoat-mandelbrot/versions/4.0 final 4.0 version], it's now waiting for reviews.
* I updated German L10n of DOM Inspector to current trunk, as well as dom/ and suite/ localizations on -central.
*As usual, [http://home.kairo.at/blog/ my blog] has more detailed status about my activities, and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/KaiRo/posts Mozilla Status Board Posts] also tell about my next planned steps - both including my non-SeaMonkey Mozilla work as well.
==== mcsmurf ====
==== mcsmurf ====
==== Misak ====
==== Misak ====
Line 229: Line 246:


==== Mnyromyr ====
==== Mnyromyr ====
Current:
Current:
* {{Bug|356742}} [cocoa] Sheets are offscreen if opened when all windows closed
* {{Bug|610509}} Make fullscreen mode really fullscreen.
* {{Bug|610509}} Make fullscreen mode really fullscreen.
* Sidebar planning


==== MReimer ====
==== MReimer ====
Line 256: Line 276:
==== Ricardo ====
==== Ricardo ====
==== sgautherie ====
==== sgautherie ====
*Fixed (<i>or in-progress</i>) MailNews Core bugs:
**<i>{{bug|694371}} [c-c] "Warning: package error or possible missing or unnecessary file:" : 4 "VC80" files</i>
==== Stanimir ====
==== Stanimir ====
Done:
Done:
Line 266: Line 289:
* Organized and ran a very successful SeaMonkey Halloween Bug Event (like a testday) on #bugday on the 30th of October.
* Organized and ran a very successful SeaMonkey Halloween Bug Event (like a testday) on #bugday on the 30th of October.
** Special thanks to Px and Mnyromyr for lots of bug triaging during the bug event.
** Special thanks to Px and Mnyromyr for lots of bug triaging during the bug event.
* '''TODO:'''
** Finish publishing [[SeaMonkey/Bug_events/20111027#Results|the bug event stats]].
** Announce them on NG, Members' list, etc., once they're finished.


=== Any other business?  ===
=== Any other business?  ===
* Need to review [http://www.seamonkey-project.org/dev/project-areas project areas]
* Need to review [http://www.seamonkey-project.org/dev/project-areas project areas]
** '''IanN''' will put out a final draft of the project areas list this week, and then confirm that anyone who is not in the loop already has been consulted.
** '''IanN''' has put out a final draft of the project areas list, and will then confirm that anyone who is not in the loop already has been consulted.
* Extended Support Releases (ESR)
* Extended Support Releases (ESR)
** At the moment looks like that will be based off either Gecko 8 or 9 so potentially that will be either 2.5 or 2.6 for us. Assuming we have the machines, we will also have an ESR which might help move some of those still on 2.0 up to 2.5/2.6.
** At the moment looks like that will be based off either Gecko 8 or 9 so potentially that will be either 2.5 or 2.6 for us. Assuming we have the machines, we will also have an ESR which might help move some of those still on 2.0 up to 2.5/2.6.
** Our ESR should use the same branch as Firefox ESR so any Security and Stability "extended" fixes for Gecko will be picked up by the SeaMonkey ESR.
** Our ESR should use the same branch as Firefox ESR so any Security and Stability "extended" fixes for Gecko will be picked up by the SeaMonkey ESR.
** A ESR (Extended Security Release) may not be a given for us out of the gate. Callek thinks we should revisit that, separately, once it is clearer both what Gecko it will be based on, and what MoCo's general plans for their marketing/target/ support-levels etc are.
** A ESR (Extended Security Release) may not be a given for us out of the gate. Callek thinks we should revisit that, separately, once it is clearer both what Gecko it will be based on, and what MoCo's general plans for their marketing/target/ support-levels etc are.
* We can probably start working on Geolocation. Callek hasn't verified all the minutia there yet, but if someone wants to begin work, he can devote slightly more of his time to it.
* '''Geolocation'''.
* Another bug event happened at the end of last week.
** <s>We can probably start working on this. Callek hasn't verified all the minutia there yet, but if someone wants to begin work, he can devote slightly more of his time to it.</s>
** Geolocation now works out of the box. MoCo turned it on by default for all applications that build off mozilla-central.
*** For comm-beta all we need to do is ({{Bug|494421}}) to add <tt>pref("geo.wifi.uri", "https://www.google.com/loc/json");</tt> to browser-prefs.js.
* The '''Halloween Bug Event''' happened at the end of last week.
** tonymec will be producing some stats from the event.
** Now available at [[SeaMonkey/Bug_events/20111027#Results]].
* Who is going to MozCamp Europe 2011? (sgautherie, KaiRo, mcsmurf, Mnyromyr and stefanh)
**Anything planned w.r.t. SeaMonkey?
* Who is going to MozCamp Asia 2011? (Ratty).
** Nothing planned w.r.t. SeaMonkey, but Ratty might give a lightning talk.
Confirmed users
2,595

edits

Navigation menu