MozillaWiki

SeaMonkey/StatusMeetings/2015-09-01: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2015-09-01 (view source)

Revision as of 08:20, 29 September 2015

568 bytes added ,  29 September 2015
m
My cat is sad because he saw a sharp jagged secret shard of pain in your eyes and wonders who it was who hurt you.
m (My cat is sad because he tried a new pose to try to come across as "street", but people said he looked like an idiot.)
m (My cat is sad because he saw a sharp jagged secret shard of pain in your eyes and wonders who it was who hurt you.)
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting &raquo;]]</small>
'''SeaMonkey Meeting Details'''
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=1&month=9&year=2015&hour=12&min=0&sec=0&p1=0 1 September, 2015, 12:00 UTC]
** (8am Eastern, 1pm UK, 2pm Central Europe, 8pm Hong Kong)
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
== Agenda ==
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Who's taking minutes? -> '''TBD'''
Line 9: Line 18:


'''NEW'''
'''NEW'''
* &mdash;
* Need to port Sync 2.0 to SeaMonkey - IanN to talk to ewong about options.
'''OPEN'''
'''OPEN'''
* The carousel within Add-On Manager can be used for SeaMonkey specific content. [Ratty] needs to file a bug. Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content.
* {{Bug|1198340}} The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
* {{bug|1121281}} tracks the RelEng automation migration off CVS. Everything is now in a single repo, patches for using that new repo are awaiting a review from Callek.
* {{bug|1121281}} tracks the RelEng automation migration off CVS. Everything is now in a single repo, patches for using that new repo are awaiting a review from Callek.
'''CLOSED'''
'''CLOSED'''
Line 51: Line 60:
* SeaMonkey 2.35 release:
* SeaMonkey 2.35 release:
** (ewong) is expected this week, along with, hopefully, 2.38 beta.
** (ewong) is expected this week, along with, hopefully, 2.38 beta.
 
** Once 2.35 is out Callek and ewong will focus on getting a beta of 2.38 out A.S.A.P. Due to certificate server issues, we need to do a beta release from 2.38 at the latest (2.39 would have problems).
==== SeaMonkey 2.35 Release ====
==== SeaMonkey 2.35 Release ====
* We plan to release SeaMonkey 2.35 asap in August.
* <s>We plan to release SeaMonkey 2.35 asap in August</s>. We missed this deadline but should have a release this week (September).
** For windows builds, we have a loaner win machine from Mozilla for us (i.e. ewong) to do manual window builds.
** For windows builds, we have a loaner win machine from Mozilla for us (i.e. ewong) to do manual window builds.
** (ewong): Suggesting early September, but we shall see.
** (ewong): Suggesting early September, but we shall see.
Line 62: Line 71:
** The 2.35 l10n Win32 repacks were done on late Sunday/Early Monday (30th/31st August 2015)
** The 2.35 l10n Win32 repacks were done on late Sunday/Early Monday (30th/31st August 2015)
*** The busted l10n linux/osx repacks (ca, fi, ja(linux), ja-JP-mac(osx), sv-SE, pt-PT) were retriggered on Monday 31st August 2015.
*** The busted l10n linux/osx repacks (ca, fi, ja(linux), ja-JP-mac(osx), sv-SE, pt-PT) were retriggered on Monday 31st August 2015.
===== Ratty =====
* '''IN PROGRESS''': &mdash;
** mozilla-esr38: Regularly merge default branch to SEAMONKEY_2_35_RELEASE_BRANCH to pick up the latest stability and security fixes. We now have all the security and stability fixes that are now in Gecko 38.2+.
* '''TO DO''': &mdash;


=== Extensions and Plugins Compatibility Tracking ===
=== Extensions and Plugins Compatibility Tracking ===
Line 119: Line 123:
* [http://www.seamonkey-project.org/releases/seamonkey2.36/ SeaMonkey 2.36 Release Notes] ''(yet to come)''
* [http://www.seamonkey-project.org/releases/seamonkey2.36/ SeaMonkey 2.36 Release Notes] ''(yet to come)''
* SEAMONKEY_2_36_RELEASE_BRANCH has been established in comm-release.
* SEAMONKEY_2_36_RELEASE_BRANCH has been established in comm-release.
* [Ratty] We will probably skip to SeaMonkey 2.37 after releasing SeaMonkey 2.35.
* [Ratty] We will probably skip to '''SeaMonkey 2.38''' after releasing SeaMonkey 2.35.


==== 2.Next ====
==== 2.Next ====
* We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in:
** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
** {{Bug|1003434}} Add support for about:sync-progress.
<!-- *** '''We have official permission to use the Firefox FxA 2.0 sync servers!''' -->
* Stalled. Needs a kick.
* Stalled. Needs a kick.
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
Line 130: Line 138:
<!--Please update-->
<!--Please update-->
* Mozilla-central bugs that affect us:
* Mozilla-central bugs that affect us:
** Change to Safe Browsing
** Changes to Safe Browsing
** Change of printing API {{bug|1146454}} needs to be ported, immediate bustage was fixed in {{bug|1190344}}.
** Change of printing API {{bug|1146454}} needs to be ported, immediate bustage was fixed in {{bug|1190344}}.
*** IanN is looking to migrate comm-central to the new API.
*** IanN is working on migrating comm-central to the new API [{{Bug|1195863}}].
** Change of add-on installation whitelist from a pref to permissions manager, {{bug|1072751}}:
*** {{Bug|1190233}} "Default" permissions being added to an existing profile without user's consent or awareness.
*** some confusion whether or not they should be picked up by ''existing'' profiles or just by new ones.
*** patch ready for checkin and received branch approval to remove FF-specific sites from the current whitelist.
*** '''FIXED''' (thanks to Ratty for checking the patch in on all branches!)
** Firefox is currently changing styles of several Toolkit pages
** Firefox is currently changing styles of several Toolkit pages
*** already affected: config.xul for about:config, {{bug|1125636}}
*** already affected: config.xul for about:config, {{bug|1125636}}
Line 144: Line 147:
*** Fallout thus far: {{bug|1133380}} about:privatebrowsing ''(Default)'', {{bug|1133582}} about:config ''(Modern)''
*** Fallout thus far: {{bug|1133380}} about:privatebrowsing ''(Default)'', {{bug|1133582}} about:config ''(Modern)''
*** further work to separate function from style in CSS for about:privatebrowsing in {{bug|1178008}} ''(3rd-party themes)''
*** further work to separate function from style in CSS for about:privatebrowsing in {{bug|1178008}} ''(3rd-party themes)''
*** '''Ratty''' is currently working on restoring about:privatebrowsing UI to before it was messed up by Project Chameleon styles [No bug number yet]
*** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}]
** Our front end Sync UI needs to be updated as the old backend is going away in Gecko/Firefox 31. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in:
*** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
*** {{Bug|1003434}} Add support for about:sync-progress.
*** Ewong has set up a PoC FxA 1.5 server but need to complete the porting of the UI from Firefox.
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
Line 180: Line 179:
*'''TODO:'''
*'''TODO:'''
** {{Bug|1127784}} proposes to add a preference and UI to enable/disable playback of Encrypted Media Extensions.
** {{Bug|1127784}} proposes to add a preference and UI to enable/disable playback of Encrypted Media Extensions.
***  '''FIXED''' has landed, with UI seen in non-release builds only
***  '''FIXED''' has landed, with UI seen in non-release builds only.
*** but uncertain if it does anything useful to be tested
*** but uncertain if it does anything useful to be tested.
* Our in content help text is badly outdated. We should import the current xhtml files into some sort of database which can then output both a set of web pages as well as the xhtml files that populate our current help content.


=== Roundtable - Personal Status Updates ===
=== Roundtable - Personal Status Updates ===
Line 239: Line 239:
==== Mnyromyr ====
==== Mnyromyr ====
==== Neil ====
==== Neil ====
Sorry, I've not done much at all this fortnight due to illness.
==== Px ====
==== Px ====
==== Rainer Bielefeld ====
==== Rainer Bielefeld ====
Philip Chee
Confirmed users
2,595

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1093119...1098110"