647
edits
Changes
status meeting notes
<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -3 week}}|« last meeting]] | [[SeaMonkey/StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 3 week}}|next meeting »]]</small>
'''SeaMonkey Meeting Details'''
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance): IanN frg rsx11m tonymec daniel__ WaltS48
== Agenda ==
* Who's taking minutes? -> '''TBDfrg'''
* Nominees for Friends of the Fish Tank:
** '''TBDSeaMonkey core team for building 2.49.5 and doing support work ewong frg IanN rsx11m'''
=== Action Items ===
* —
'''OPEN'''
* We are moving our irc presence to freenode. Please register your nick there and join us at [irc://moznet/seamonkey/ SeaMonkey feeenode irc channel].
* For future macOS releases we might need an Apple Developer ID and notarization process. See [https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution Notarizing Your App Before Distribution].
* The project areas on the website need further updates to reflect the current responsibilities after some long time developers and maintainers left the project. {{bug|1356106}} has already been filed.
** '''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.
** '''frg''' mentioned that currently this is We are planning to provide official repos on gitlab.*** Plans have not planned been finalized yet but the repos will probably be read-only and might not periodically synced with the offical mercurial repos.*** We need at least 2.53 and 2.57 repos.*** Patches will still be on the agenda in the forseeable future because of existing developer shortagesdone via bugzilla first and then checked into hg.** 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.** 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.
* —
'''CLOSED'''
* We are building up a new infrastructure using Azure.
** 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.
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* '''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.
** 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.
** Other than azure hosting options because of price are also evaluated.
<!-- Comment out this section if nothing new fixed -->
<!-- uncomment if no new stuff comes up-->
==== Fixed Infrastructure Stuff Since Last Meeting ====
* The builders on Questions about infrastructure** '''daniel''' wants to contact ewong and asking about our Azure configuration.** If the new infrastructure have been set up for local buildingbuild VMs are powered down when not in use we should save money.* Windows x86/x64, Linux x86/x64 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 macOS Test builds have been doneso stay running most of the time.<!-- end -->
=== Status of the SeaMonkey Source Tree ===
** 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.
** 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 35 is now mandatory.
** 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]:
** Do not use any current comm-beta based release.
** See {{bug|1452448}} for current comm-central breakages.
* [comm-release]:
** We currently do not track nor update comm-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 . The next release will be based on 2.53 paving the way to for 2.57.
** See {{bug|1379370}} for current 2.53 breakages. All known major bugs for 2.53 are closed.
* [comm-esr68]:
** There are currently no plans for a SeaMonkey release based on comm-esr68.
** We will not track nor update comm-esr68.
* [comm-esr60]:
** Sidebar, Help and Mail/News are broken because of XUL template removals. See {{bug|464710}}.
** 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.
* [comm-esr52]:
** See {{bug|1313304}} for current breakages.
<!-- Comment out this section if nothing new fixed -->
<!-- Close comment if new stuff comes up -->
=== Fixed Source Tree Stuff Since Last Meeting ===
* —
=== Release Train ===
** SeaMonkey 2.49.5 will be the next minor release.
*** {{bug|1512882}} tracks the 2.49.5 release.
*** '''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.** '''IanN''' candidate build 2 will be up soon and '''frg''' did should be the final fixes.*** Some late fixes are still being tested and added.** build'''IanN''' has patches for missing l10n ready.*** Late l10n additions will were 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.
*** Complete mar files have been generated. Partial update files from the previous version can probably will not be done in time.*** ''' 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.
** The following bugs are not yet fixed in 2.49.5:
*** {{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.
*** [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 ].
*** mozilla-esr52 is closed so pushes There are currently no plans to the release branch in it need to be with CLOSED TREEpush 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.
** cZ, DOMi and the Lightning extension will be 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 will be are done.
** '''frg''' has backported the ESR60 MAPI fixes for the x64 Windows release.
** '''frg''' did backport all but 3 ESR60.2 fixes.
** ''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.
** 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.
*** 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.
**** 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 version if needed.**** Because we are using cross compiling we will provide an a 2.49.5 x64 macOS build only.
** Building with the 10.11 SDK need the fixes in {{bug|1391790}} for macOS 10.13.
** Unofficial Linux builds just need to will be declared official.** Providing Windows x64 builds is tracked in {{Bug|482143}}which will be closed after the 2.49.** Release notes need to be done5 release.** '''frg''' started doing did the release notes. ** 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.
* SeaMonkey 2.53 / Gecko 56 in comm-release with unoffical patches.
** 2.53 will become 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.
*** '''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''' 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.
** 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}}.
** WebExtentions dictionary support should be enabled as soon as possible in 2.53.
* SeaMonkey 2.57 Gecko 60 in comm-esr60.
** SeaMonkey 2.57 will be the next major release 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.
** 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.78.10).
** 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.
*** {{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.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
=== Extensions and Plugins Compatibility Tracking ===
* 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.
* 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.
=== 2.x (Last, Current, Next) ===
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
[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.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 -->
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey257esr&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
=== Any other business? ===
* The next meeting will be held in two three weeks on Sunday August 411, 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.
* —
