SeaMonkey/StatusMeetings/2012-05-15: Difference between revisions

m
 
(5 intermediate revisions by 2 users not shown)
Line 25: Line 25:


=== Status of the SeaMonkey Buildbot Master and Tree ===
=== Status of the SeaMonkey Buildbot Master and Tree ===
* All our machines are out of SJC1 are are now at SCL3 or SCL1. Everything that '''was''' up as of 2 months ago is up now. Callek still needs to set up some machines including our R4 Macs.
* ewong and Callek are looking into building on MSVC2010 by Friday.
* ewong and Callek are looking into building on MSVC2010 by Friday.
* tonymec is worried about status of trunk l10n: 7 languages not built since Apr 27, the other 14 currently only on Linux. This is probably related to the server moves going on.
* tonymec is worried about status of trunk l10n: 7 languages not built since Apr 27, the other 14 currently only on Linux. This is probably related to the server moves going on.
** '''Update''' (2012-05-20): l10n buildbots are building again on all three platforms for be, de, en-GB, es-AR, gl, hu, it, lt, nl, ru, sk, uk, zh-CN and zh-TW. Still nothing since end of April for cs, es-ES, fr, nb-NO, pl, pt-PT and sv-SE.


=== Release Train ===
=== Release Train ===
Line 38: Line 40:
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
** Nothing special this time.
** Nothing special this time.
* [[DOM_Inspector/Releases|DOM Inspector Release Schedule]] (crussell)
** {{Bug|746784}} Predictable release schedule for development and localization.
** The last six weeks of a release cycle are for localizers no string changes will occur then. Localization happens on a branch (DOMI_2_0_12 right now) and concurrent development happens on default. Right now, DOM Inspector is set to ship with: de, el, en-GB, en-US, fr, ru, sk, sv-SE.
** Serge has filed some bugs so that the relevant changes to pull the right branch are in place. See {{Bug|732749}} (client.py: review SeaMonkey policy about which extension revisions are packaged).
** So in theory we could work out the correct tag from the Gecko version of the repos we're building in? It's not tagged it's just a branch. To get on the right branch:
  hg clone http://hg.mozilla.org/dom-inspector
  cd ./dom-inspector
  hg update DOMI_2_0_12
** It is to be hoped that our build team (Serge, Callek, ewong) can sort it out so it is fairly automated rather than having to tweak the client.py every 6 weeks.


=== 2.x (Last, Current, Next) ===
=== 2.x (Last, Current, Next) ===
Line 51: Line 62:
** There seems to be a very small number of 2.0.x users on OSes not supported by later versions. We even have some users on windows 7 using 2.0x! Fortunately Windows 8 users are at least using 2.7.
** There seems to be a very small number of 2.0.x users on OSes not supported by later versions. We even have some users on windows 7 using 2.0x! Fortunately Windows 8 users are at least using 2.7.
** Darwin 9.8 is last version with PPC support, so those people may stuck on old versions because of that.
** Darwin 9.8 is last version with PPC support, so those people may stuck on old versions because of that.
*** For OSX/PPC I wonder if someone from the community could try building a contributed "TenFourMonkey" based on the patch sets from TenFourFox plus TenFourBird [Ratty].
*** [http://code.google.com/p/seamonkey-ppc/downloads/list SeaMonkey 2.6.1 for a PowerPC/G4 on Mac OS 10.5.x]. IanN says we should advertise that more (and other contributed builds).
** Ian has done some working on comparing profile of 2.0.x users against 2.9 ones.
** Ian has done some working on comparing profile of 2.0.x users against 2.9 ones.
*** Split between OS for 2.9 is Windows 92.82%, Linux 2.53%, MacOS 4.65% and for 2.0.x is Windows 85.37%, Linux 5.55%, MacOS 9.08%.
*** Split between OS for 2.9 is Windows 92.82%, Linux 2.53%, MacOS 4.65% and for 2.0.x is Windows 85.37%, Linux 5.55%, MacOS 9.08%.
Line 68: Line 81:
** Callek now needs to morph {{bug|667147}} into removing |ka| from our [current] automation entirely (all-locales). Callek will look at best locale to transition any ka users to.
** Callek now needs to morph {{bug|667147}} into removing |ka| from our [current] automation entirely (all-locales). Callek will look at best locale to transition any ka users to.
*** Plan is to migrate ka users to en-US with a english dialog saying they are out of date, and a link to the all-locales page if there is a language they understand better. Current ADU of ka alone is 3-5 individuals, so low impact.~Callek
*** Plan is to migrate ka users to en-US with a english dialog saying they are out of date, and a link to the all-locales page if there is a language they understand better. Current ADU of ka alone is 3-5 individuals, so low impact.~Callek
*** Callek and ewong are working on this and they should be able to get this done by the time 2.9 ships.
*** Callek and ewong were working on this but they didn't manage to get this done by the time 2.9 shipped. No new ETA unfortunately.
* One regression issue noted for 2.8: {{Bug|735946}} Browser is not not focused when opening links from external applications. Fixed on 2.9+.
* One regression issue noted for 2.8: {{Bug|735946}} Browser is not not focused when opening links from external applications. Fixed on 2.9+.


Confirmed users
704

edits