MozillaWiki

SeaMonkey/StatusMeetings/2019-07-21: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2019-07-21 (view source)

Revision as of 20:03, 21 July 2019

4,127 bytes added ,  21 July 2019
→‎Action Items: freenode is new
(→‎Release Train: updates for Gecko 70 merge and ESR68 branch)
(→‎Action Items: freenode is new)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -3 week}}|&laquo; last meeting]] | [[SeaMonkey/StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting &raquo;]]</small>
<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -3 week}}|&laquo; last meeting]] | [[SeaMonkey/StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +3 week}}|next meeting &raquo;]]</small>


'''SeaMonkey Meeting Details'''
'''SeaMonkey Meeting Details'''
Line 7: Line 7:
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance):  
* Participants (in order of appearance): IanN frg rsx11m tonymec daniel__ WaltS48
 
== Agenda ==
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Who's taking minutes? -> '''frg'''
* Nominees for Friends of the Fish Tank:
* Nominees for Friends of the Fish Tank:
** '''TBD'''
** '''SeaMonkey core team for building 2.49.5 and doing support work ewong frg IanN rsx11m'''


=== Action Items ===
=== Action Items ===
Line 18: Line 19:


'''NEW'''
'''NEW'''
* We are moving our irc presence to freenode. Please register your nick there and join us at [irc://moznet/seamonkey/ SeaMonkey feeenode irc channel].
* &mdash;
* &mdash;
'''OPEN'''
'''OPEN'''
Line 32: Line 34:
** '''ewong''' has been looking at Kallithea, RhodeCode and other similar tools which are needed later to automate source code management for non mozilla repos (tools, website and others).
** '''ewong''' has been looking at Kallithea, RhodeCode and other similar tools which are needed later to automate source code management for non mozilla repos (tools, website and others).
* '''daniel''' asked if there are any plans to provide github repos to attract new developers.
* '''daniel''' asked if there are any plans to provide github repos to attract new developers.
** '''frg''' mentioned that currently this is not planned and might not be on the agenda in the forseeable future because of existing developer shortages.
** We are planning to provide official repos on gitlab.
** Mozilla does this to a degree and we don't rule it out in the future. See [https://github.com/mozilla/gecko-dev/ Mozilla gecko-dev repo] as an example.
*** Plans have not been finalized yet but the repos will probably be read-only and periodically synced with the offical mercurial repos.
*** We need at least 2.53 and 2.57 repos.
*** Patches will still be done via bugzilla first and then checked into hg.
** Mozilla does this to a degree. See [https://github.com/mozilla/gecko-dev/ Mozilla gecko-dev repo] as an example.
** Gitlab was choosen because it actually works with SeaMonkey out of the box and the current developer nicks were not taken.
*** Github needs a user override and is not very friendly to unknown or browsers it does not want to support. SeaMonkey users might not be able to use it in the near future at all.
** With git we would be able to integrate gitlab into our infrastructure.
* &mdash;
* &mdash;
'''CLOSED'''
'''CLOSED'''
Line 42: Line 50:
* We are building up a new infrastructure using Azure.
* We are building up a new infrastructure using Azure.
** Jenkins will be set up on the builders in parallel to not delay further releases.
** Jenkins will be set up on the builders in parallel to not delay further releases.
*** Also evaluation of Ansible and Terraform going together with it is done.
** '''ewong''' waits for info from '''mhoye''' to be able to work out traffic requirements.
** '''ewong''' waits for info from '''mhoye''' to be able to work out traffic requirements.
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* '''daniel''' wants to contact ewong and asking about our Azure configuration.
** If the build VMs are powered down when not in use we should save money.
* '''frg''' thinks we should move the config files for building out of the source tree as much as possible.
* '''frg''' thinks we should move the config files for building out of the source tree as much as possible.
** '''IanN''' remarked that they are tied to the version in the tree.
** '''IanN''' remarked that they are tied to the version in the tree.
** Discussion for later when setting up jenkins. Even buildbot had some version specific files outside the tree.
** Discussion for later when setting up jenkins. Even buildbot had some version specific files outside the tree.
* Some Capacity planning to find the best price/performance ratio is carried out.
* Some Capacity planning to find the best price/performance ratio is carried out.
** Other than azure hosting options because of price are also evaluated.
<!-- Comment out this section if nothing new fixed -->
<!-- Comment out this section if nothing new fixed -->
<!-- uncomment if no new stuff comes up
<!-- uncomment if no new stuff comes up -->
==== Fixed Infrastructure Stuff Since Last Meeting ====
==== Fixed Infrastructure Stuff Since Last Meeting ====
* The builders on the new infrastructure have been set up for local building.
* Questions about infrastructure
* Windows x86/x64, Linux x86/x64 and macOS Test builds have been done.
** '''daniel''' wants to contact ewong and asking about our Azure configuration.
end -->
** If the build VMs are powered down when not in use we should save money.
* A: We are not very good at it but we do shutdown vms when not in use. Currently there are used alot for building and so stay running most of the time.
<!-- end -->


=== Status of the SeaMonkey Source Tree ===
=== Status of the SeaMonkey Source Tree ===
Line 70: Line 80:
** New builds tools are needed to compile comm-central. Latest addition is nasm which will replace the unmaintained yasm.
** New builds tools are needed to compile comm-central. Latest addition is nasm which will replace the unmaintained yasm.
** See {{bug|1452448}} for current comm-central breakages. This is not up to date.
** See {{bug|1452448}} for current comm-central breakages. This is not up to date.
** msvc VS2017 is no longer supported for building under Windows. It still needs to be installed but clang-cl is used as the compiler.
** msvc VS2017 is no longer supported for building under Windows. It or VS2019 still needs to be installed but clang-cl is used as the compiler.
** Rust 1.34 is now mandatory.
** Rust 1.35 is now mandatory.
** Fix for {{bug|1300198}} will unbreak the comm-central l10n builds.
** Fix for {{bug|1300198}} will unbreak the comm-central l10n builds.
** macOS building is currently broken. Bill provided a fix but '''frg''' didn't have time to unbreak it yet.


* [comm-beta]:
* [comm-beta]:
Line 78: Line 89:
** Do not use any current comm-beta based release.
** Do not use any current comm-beta based release.
** See {{bug|1452448}} for current comm-central breakages.
** See {{bug|1452448}} for current comm-central breakages.
* [comm-release]:
* [comm-release]:
** We currently do not track nor update comm-release.
** We currently do not track nor update comm-release.
** Do not use any current comm-release based release.
** Do not use any current comm-release based release.
** An updated unofficial 2.53 is available from [http://www.wg9s.com/comm-253/ WG9's website]. We accept filing bugs against it but it is only provided for testing purposes on the way to 2.57.
** An updated unofficial 2.53 is available from [http://www.wg9s.com/comm-253/ WG9's website]. We accept filing bugs against it. The next release will be based on 2.53 paving the way for 2.57.
** See {{bug|1379370}} for current 2.53 breakages. All known major bugs for 2.53 are closed.
** See {{bug|1379370}} for current 2.53 breakages. All known major bugs for 2.53 are closed.
* [comm-esr68]:
* [comm-esr68]:
** There are currently no plans for a SeaMonkey release based on comm-esr68.
** There are currently no plans for a SeaMonkey release based on comm-esr68.
** We will not track nor update comm-esr68.
** We will not track nor update comm-esr68.
* [comm-esr60]:
* [comm-esr60]:
** Sidebar, Help and Mail/News are broken because of XUL template removals. See {{bug|464710}}.
** Sidebar, Help and Mail/News are broken because of XUL template removals. See {{bug|464710}}.
Line 93: Line 107:
** If you want to use Rust 1.33 and up you need the patches available on Bills site.
** If you want to use Rust 1.33 and up you need the patches available on Bills site.
** See {{bug|1433370}} for current 2.57 breakages.
** See {{bug|1433370}} for current 2.57 breakages.
* [comm-esr52]:
* [comm-esr52]:
** See {{bug|1313304}} for current breakages.
** See {{bug|1313304}} for current breakages.
Line 99: Line 114:


<!-- Comment out this section if nothing new fixed -->
<!-- Comment out this section if nothing new fixed -->
<!-- Close comment if new stuff comes up -->
<!-- Close comment if new stuff comes up
=== Fixed Source Tree Stuff Since Last Meeting ===
=== Fixed Source Tree Stuff Since Last Meeting ===
* Bug {{bug|1559407}} fixed the broken comm-central tree.
* &mdash;
* &mdash;
<!-- Open comment if no new stuff comes up -->
Open comment if no new stuff comes up -->


=== Release Train ===
=== Release Train ===
Line 109: Line 123:
** SeaMonkey 2.49.5 will be the next minor release.
** SeaMonkey 2.49.5 will be the next minor release.
*** {{bug|1512882}} tracks the 2.49.5 release.
*** {{bug|1512882}} tracks the 2.49.5 release.
*** '''candidate build 1 is up on the mozilla.org staging site'''  
*** '''candidate build 1 is up on the mozilla.org staging site'''.
** The first manual test builds have been done on the new infrastructure. The release is not around the door but shouldn't be delayed much longer.
*** '''candidate build 2 will be up soon and should be the final build'''.
** '''IanN''' and '''frg''' did the final fixes.
*** Late l10n additions were not added to the repos. They will be hosted on the servers for building only and be provided as archives for Linux distributions together with the source.
*** Some late fixes are still being tested and added.
** '''IanN''' has patches for missing l10n ready.
*** Late l10n additions will not be added to the repos. They will be hosted on the servers for building only and be provided as archives for Linux distributions together with the source.
** '''ewong''' will probably need to do some fixing so that the builds could be uploaded.
** '''ewong''' will probably need to do some fixing so that the builds could be uploaded.
*** Complete mar files have been generated. Partial update files from the previous version can probably not be done in time.
*** Complete mar files have been generated. Partial update files from the previous version will not be done.
*** ''' ewong''' is planning to upload candidate builds to archive.mozilla.org as soon as possible.
** {{Bug|1489785}} has been fixed in 2.49.5. Upgrading to macOS 10.14 and up should be ok.
** {{Bug|1489785}} has been fixed in 2.49.5. Upgrading to macOS 10.14 and up should be ok.
** The following bugs are not yet fixed in 2.49.5:
** The following bugs are not fixed in 2.49.5:
*** {{Bug|1409458}} "Privacy Issue: Replying to or forwarding an HTML e-mail with external content".
*** {{Bug|1409458}} "Privacy Issue: Replying to or forwarding an HTML e-mail with external content".
*** {{Bug|1406049}} is fixed in comm-esr60 but has a limited audience and backporting would need too many changes. {{Bug|1533894}} which fixes it is backported to 2.53.
*** {{Bug|1406049}} is fixed in comm-esr60 but has a limited audience and backporting would need too many changes. {{Bug|1533894}} which fixes it is backported to 2.53.
Line 128: Line 138:
*** [https://hg.mozilla.org/releases/comm-esr52/shortlog/SEAMONKEY_2_49_ESR_RELBRANCH SEAMONKEY_2_49_ESR_RELBRANCH ].
*** [https://hg.mozilla.org/releases/comm-esr52/shortlog/SEAMONKEY_2_49_ESR_RELBRANCH SEAMONKEY_2_49_ESR_RELBRANCH ].
*** [https://hg.mozilla.org/releases/mozilla-esr52/shortlog/SEAMONKEY_2_49_ESR_RELBRANCH SEAMONKEY_2_49_ESR_RELBRANCH ].
*** [https://hg.mozilla.org/releases/mozilla-esr52/shortlog/SEAMONKEY_2_49_ESR_RELBRANCH SEAMONKEY_2_49_ESR_RELBRANCH ].
*** mozilla-esr52 is closed so pushes to the release branch in it need to be with CLOSED TREE.
*** There are currently no plans to push further patches.
*** The new fixes and backported security fixes can be found in {{bug|1512882}}. The older TB52 verbranch fixes are in the mozilla-esr52 branch for SeaMonkey.
*** The new fixes and backported security fixes can be found in {{bug|1512882}}. The older TB52 verbranch fixes are in the mozilla-esr52 branch for SeaMonkey.
** cZ, DOMi and the Lightning extension will be included using a workaround for the l10n problem tracked in {{bug|1231349}}.
** cZ, DOMi and the Lightning extensions are included using a workaround for the l10n problem tracked in {{bug|1231349}}.
*** '''frg''' has a patch ready for the comm-esr52 SEAMONKEY_2_49_ESR_RELBRANCH to bring it up to the default branch for this. We no longer need the workarounds in the branch.
** Official Linux and Windows x64 builds are done.
** Official Linux and Windows x64 builds will be done.
** '''frg''' has backported the ESR60 MAPI fixes for the x64 Windows release.
** '''frg''' has backported the ESR60 MAPI fixes for the x64 Windows release.
*** The MAPI fixes will only be pushed to the release branch because they touch Thunderbird files.
** '''frg''' did backport all but 3 ESR60.2 fixes.
** '''frg''' did backport all but 3 ESR60.2 fixes.
** ''IanN''' backported the recent Firefox 67.0.3 security fix for bug {{bug|1544386}}.
** ''IanN''' backported the recent Firefox 67.0.3 security fix for bug {{bug|1544386}}.
** '''frg''' also backported support for VS2017 and the latest Windows toolkit to 2.49. VS2017 will be used for building 2.49.5.
** '''frg''' also backported support for VS2017 and the latest Windows toolkit to 2.49. VS2017 will be used for building 2.49.5.
** The 2.49 branch will become EOL after doing 2.49.5. Updating two branches and also fixing up 2.57 for the next release takes too much time.
** The 2.49 branch will become EOL after doing 2.49.5. Updating two branches and also fixing up 2.57 for the next release takes too much time.
*** Plan is to get l10n working for 2.53 and use this for releases after 2.49.5.
*** 2.49.5 will be the last release supporting Windows XP, Vista and Linux x86.
*** 2.49.5 will be the last release supporting Windows XP, Vista and Linux x86.
**** The older Windows versions are no longer supported in Gecko.
**** The older Windows versions are no longer supported in Gecko.
**** All major Linux distributions are now 64 bit only and we do not have the resources to support outdated distributions. Linux x64 will stay fully supported.
**** All major Linux distributions are now 64 bit only and we do not have the resources to support outdated distributions. Linux x64 will stay fully supported.
**** No Linux x86 code will be taken out. So it would still be possible to compile a x86 Linux versions if needed.
**** No Linux x86 code will be taken out. So it would still be possible to compile a x86 Linux version if needed.
**** Because we are using cross compiling we will provide an 2.49.5 x64 macOS build only.
**** Because we are using cross compiling we will provide a 2.49.5 x64 macOS build only.
** Building with the 10.11 SDK need the fixes in {{bug|1391790}} for macOS 10.13.
** Building with the 10.11 SDK need the fixes in {{bug|1391790}} for macOS 10.13.
** Unofficial Linux builds just need to be declared official.
** Unofficial Linux builds will be declared official.
** Providing Windows x64 builds is tracked in {{Bug|482143}}.
** Providing Windows x64 builds is tracked in {{Bug|482143}} which will be closed after the 2.49.5 release.
** Release notes need to be done.
** '''frg''' did the release notes.
** '''frg''' started doing the release notes. The website downloads section needs to be changed for the new x64 builds.
** The website downloads section needs to be changed for the new x64 builds.
*** '''IanN''' provided patches for the download code to enable Linux and Windows x64 build.
** The Safebrowsing V2 api SeaMonkey is using has been discontinued by google. V4 is already in 2.53 and will be used there.
** The Safebrowsing V2 api SeaMonkey is using has been discontinued by google. V4 is already in 2.53 and will be used there.


* SeaMonkey 2.53 / Gecko 56 in comm-release with unoffical patches.
* SeaMonkey 2.53 / Gecko 56 in comm-release with unoffical patches.
** 2.53 will become the next release after 2.49.5. Details are still being worked out.
** 2.53 will be the next release after 2.49.5. Details are still being worked out.
** A release would need l10n translations. The temporary solution for 2.57 will not work for this release.
** A release would need l10n translations. The temporary solution for 2.57 will not work for this release.
*** '''frg''' made a '''de''' 2.53 language pack for testing. It is available from [https://seamonkeyde.wordpress.com/2019/01/03/inoffizielles-deutsches-sprachpaket-fuer-aktuelle-seamonkey-2-53/ Rainer Bielefelds website].
*** '''frg''' made a '''de''' 2.53 language pack for testing. It is available from [https://seamonkeyde.wordpress.com/2019/01/03/inoffizielles-deutsches-sprachpaket-fuer-aktuelle-seamonkey-2-53/ Rainer Bielefelds website].
Line 168: Line 176:
** '''frg''' will do a preliminary 2.53 landing page for the website.
** '''frg''' will do a preliminary 2.53 landing page for the website.
** The safebrowsing V4 api and list fetches are now working in 2.53 and up.
** The safebrowsing V4 api and list fetches are now working in 2.53 and up.
** Lighthing caldav support is broken in 2.53. '''frg''' will try to unbreak it asap. It seems that Lightning is only needing further backports for this.
** '''IanN''' will look into including My and pt-BR locales. '''frg''' can create patches based on l10n-release and l10n-central suite but these would need to be manually fixed by the translators and checked into a comm-release branch. We did this with nb-NO in {{bug|1391174}}.
** '''IanN''' will look into including My and pt-BR locales. '''frg''' can create patches based on l10n-release and l10n-central suite but these would need to be manually fixed by the translators and checked into a comm-release branch. We did this with nb-NO in {{bug|1391174}}.
** WebExtentions dictionary support should be enabled as soon as possible in 2.53.
** WebExtentions dictionary support should be enabled as soon as possible in 2.53.


* SeaMonkey 2.57 Gecko 60 in comm-esr60.
* SeaMonkey 2.57 Gecko 60 in comm-esr60.
** SeaMonkey 2.57 will be the next major release as soon as possible.
** SeaMonkey 2.57 will be devdeloped together with 2.53 and then released as soon as possible.
*** Because of not enough developers this is a slow go and we will distribute 2.53 as an interim version.
*** Because of not enough developers this is a slow go and we will distribute 2.53 as an interim version.
** 2.57 will be build from the '''comm-esr60''' repo.
** 2.57 will be build from the '''comm-esr60''' repo.
** Mail and news are still broken in SeaMonkey 2.57 (Thunderbird is now at 60.7.1).
** Mail and news are still broken in SeaMonkey 2.57 (Thunderbird is now at 60.8.0).
** Not all patches with l10n-relevant string changes are done for 2.57. '''frg''' has figured out a way to do this using strings from later l10n-central releases (suite directory only). He tried this with a local l10n dir and it turned out ok.
** Not all patches with l10n-relevant string changes are done for 2.57. '''frg''' has figured out a way to do this using strings from later l10n-central releases (suite directory only). He tried this with a local l10n dir and it turned out ok.
*** '''IanN''' will test it later but there is currently no alternative presented.
*** '''IanN''' will test it later but there is currently no alternative presented.
Line 202: Line 211:
*** {{Bug|1271761}} Add CPU features/detection to update URL.
*** {{Bug|1271761}} Add CPU features/detection to update URL.
** Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
** Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
** Windows x64 releases
** Unofficial (contributed build) Win64 builds work.
*** Currently tracked by {{bug|482143}}.
*** Mapi {{bug|393302}} has been fixed so there is nothing more which would prevent us from releasing a fully functional Windows x64 build.


* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
Line 212: Line 217:


=== Extensions and Plugins Compatibility Tracking ===
=== Extensions and Plugins Compatibility Tracking ===
<!-- to be uncommented (and possibly moved down) at next meeting
* "Duplicate this Tab" (last updated in April 2016) is broken (mostly does nothing) even in 2.53. Not tested recently on earlier branches.
[[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 05:50, 5 December 2018 (UTC) -->
* Most extensions are now broken in SeaMonkey 2.54+ because of Mozilla api removals.
* Most extensions are now broken in SeaMonkey 2.54+ because of Mozilla api removals.
** '''WG9s''' fixed ChatZilla for 2.57. The patches have been reviewed and checked in.
** '''WG9s''' fixed ChatZilla for 2.57. The patches have been reviewed and checked in.
Line 266: Line 268:
* Mozilla removed all classic add-ons from AMO. '''Rainer_Bielefeld''' filed {{Bug|1517828}} to see if missing add-ons can be re-added. The add-on converter also no longer works because of this.
* Mozilla removed all classic add-ons from AMO. '''Rainer_Bielefeld''' filed {{Bug|1517828}} to see if missing add-ons can be re-added. The add-on converter also no longer works because of this.
** Suggestion is to use a third party archive [https://github.com/JustOff/ca-archive/ ca-archive] and xpi.
** Suggestion is to use a third party archive [https://github.com/JustOff/ca-archive/ ca-archive] and xpi.
=== 2.x (Last, Current, Next) ===
=== 2.x (Last, Current, Next) ===
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
Line 280: Line 283:
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey249&f2=target_milestone&f5=cf_status_seamonkey248&v2=2.49 fixed] (92)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey249&f2=target_milestone&f5=cf_status_seamonkey248&v2=2.49 fixed] (92)


==== 2.57.x next release branch ====
==== 2.53.x next release branch ====
<!-- NOTE: Flag fields don't contain "esr" at the end -->
<!-- NOTE: Affected is set in a lot of bugs but the fixes are in the private branch already.  -->
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey253&type0-0-0=equals&value0-0-0=%2B open tracking] (1)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey253&type0-0-0=equals&value0-0-0=%3F tracking requests] (14)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.53 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey253&f2=target_milestone&f5=cf_status_seamonkey249&v2=2.53 fixed] (30)
 
==== 2.57.x next esr release branch ====
<!-- NOTE: Target Milestone field doesn't contain "esr" at the end -->
<!-- NOTE: Target Milestone field doesn't contain "esr" at the end -->
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey257esr&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey257esr&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
Line 364: Line 375:
==== ewong ====
==== ewong ====
==== frg ====
==== frg ====
Most work for SeaMonkey in the last two weeks was again finalizing 2.49.5, doing reviews and backporting bugs to 2.53. We now have a what we consider final 2.49.5 build for all platforms.
Waiting for review:
* {{Bug|1274798}} Seamonkey integration in Gnome3. Old bug/patch which needs verification from someone more familiar with Linux.
* {{Bug|1512890}} Create/Update 2.49.5 Release Notes. Need to incorporate feedback and do a follow-up for the website. Needs a part 2 with the new x64 download options added.
Waiting for esr60 a+:
* Nothing
Waiting for feedback:
* {{Bug|1410646}} Fix SM "log into/onto" and related instances.
Checkin ready:
* {{Bug|1374094}} Clean up debugQA. Will get a follow-up to add a new developer page. Somewhat delayed.
Reviewing:
* {{Bug|1536779}} Port |Bug 1528840 - addressingWidgetOverlay.js, abMailListDialog.js code cleanup| to SeaMonkey. A little on the backburner.
Working on:
* Plan to fix Lightning in 2.53 for caldav next. Works in 2.57 so probably only needs backports.
* {{Bug|1231349}} l10n repacks broken on with SM 2.42 and newer. cZ patch done for 2.57 and up. Got feedback but found a bug yesterday. Backport to 2.53 later.
* {{Bug|1231349}} l10n repacks broken on with SM 2.42 and newer. DOMi patch mostly working. cZ got f+. Shooting for r+ next.
* Doing local 2.53 l10n builds to assess how much would be missing for a possible release.
* Fixing up mailnews for 2.57. Starting to see if I can back out the xul templates removal to speed things up. Second bug backed out but still no luck.
* Backporting ESR 60 fixes to 2.53. At 60.3 now.
* {{Bug|521861}} After creating news account through clicking news URL Account Wizard is broken. '''jorgk''' found some issues in the patch which I need to fix first.
* Integrating DOMi Plus patches into DOMi.
* Port of {{Bug|1100103}} Add a remove button to every To/CC/BCC address in Composer. No bug yet. Initial version in 2.53. Needs better styling.
Not working on:
* Fixing comm-central. Not worth it currently. Only see that it builds.
** 2.58+ is broken in capital letters as in BROKEN.
Shelved for later:
* {{Bug|1296850}} Show standard loading indicator images in tab when busy or progress attribute are set. Asked someone who wants to help out to look at the icons. Got the icons but have no time at the moment.
* {{Bug|1379062}} Enable cross-compile on SeaMonkey Linux machines. 2.49.x to 2.57 compiles fine locally.
* {{Bug|1392929}} Port Bug 886907 [Remove old synchronous contentPrefService] to SeaMonkey.
* Followups for {{Bug|1379369}} to TriggeringPrincipals and UserContextIDs in more functions.
* {{Bug|1370314}} SeaMonkey 06/2017 installer rollup. Probably not much more right now. Took some parts to other bugs. and will see what is left when 2.57 is ready.
* Helping '''MMR''' with {{Bug|1444740}} Drop support for -moz-border-*-colors in SeaMonkey. He seems to have dropped out :(
Titbits:
* Paid work and traveling too away most of my time in the last two weeks. Not able to do much.
==== IanN ====
==== IanN ====
==== Rainer Bielefeld ====
==== Rainer Bielefeld ====
Line 379: Line 434:


=== Any other business? ===
=== Any other business? ===
* The next meeting will be held in two weeks on Sunday August 4, 2019, 14:00 UTC (16:00 CET).
* The next meeting will be held in three weeks on Sunday August 11, 2019, 14:00 UTC (16:00 CET).
** After the meeting '''IanN''' found out the he double booked himself. The meeting might need to be rescheduled.
* We plan to hold the meetings using freenode irc starting Sunday September 1, 2019. Watch this space after the next weeting for further announcements.
* &mdash;
* &mdash;
Frg
647

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1215299...1215364"