MozillaWiki - Recent changes [en]

NightlyCrashTriage/2026Q2

2026-06-11T23:20:59Z

June 10 and 11 Nightlies

← Older revision		Revision as of 23:20, 11 June 2026
Line 1:		Line 1:
			== 2026-06-11 - mccr8 ==
			June 10 and 11 Nightlies
			* Filed: {{Bug\|2047014}} - Crash in [@ <wgpu_hal::vulkan::descriptor::DescriptorAllocator as core::ops::drop::Drop>::drop].
			* Filed: {{Bug\|2047016}} - Crash in [@ mozilla::VideoFramePool<T>::GetVideoFrameSurface].
			* Filed: {{Bug\|2047017}} - Crash in [@ webrender_bindings::moz2d_renderer::impl$7::prepare_request::maybe_crash_on_no_font_file].

	== 2026-04-10 - mccr8 ==		== 2026-04-10 - mccr8 ==
	April 8 and 9 Nightlies		April 8 and 9 Nightlies

Security/Cipher Suites

2026-06-11T23:18:36Z

Indicating new locations for the Cipher Suite content

Show changes

Security/Server Side TLS

2026-06-11T23:17:09Z

Indicating new locations for the Server Side TLS page

Show changes

User Services/Sync

2026-06-11T17:48:54Z

replaced previous obsoleting with {{ OBSOLETE CONTENT }} banner

← Older revision		Revision as of 17:48, 11 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	{{~~LastUpdated}}~~		{{ OBSOLETE CONTENT }}

	~~{{warning\|This page is obsolete, please go to [[CloudServices]].~~}}

	The new home of all things related to the design & development of the '''New Sync''' service that is slated to replace the existing Sync service in late 2013/early 2014. A working name for this project has been PiCL ("Profile in the Cloud"), and the below documents may use this acronym.		The new home of all things related to the design & development of the '''New Sync''' service that is slated to replace the existing Sync service in late 2013/early 2014. A working name for this project has been PiCL ("Profile in the Cloud"), and the below documents may use this acronym.

Services/Sync/Server

2026-06-11T17:08:04Z

deprecated at heading level

← Older revision		Revision as of 17:08, 11 June 2026
(One intermediate revision by the same user not shown)
Line 9:		Line 9:
	* [https://artemis.sh/2023/03/27/firefox-syncstorage-rs.html syncstorage-rs instructions for various distros], by Artemis. (external)		* [https://artemis.sh/2023/03/27/firefox-syncstorage-rs.html syncstorage-rs instructions for various distros], by Artemis. (external)

	= Python implementation =		= Python implementation (deprecated) =

	Information related to the 2012-ish Python implementation of the Sync server:		Information related to the now-deprecated 2012-ish Python implementation of the Sync server:

	* [[Services/Sync/Server/DesignNotes\|Design notes]]		* [[Services/Sync/Server/DesignNotes\|Design notes]]

Standards/w3c-interest-community-groups

2026-06-11T15:25:55Z

+Web Machine Learning Community Group

← Older revision		Revision as of 15:25, 11 June 2026
Line 98:		Line 98:
	https://www.w3.org/community/wfcg/		https://www.w3.org/community/wfcg/
	* <span class="h-card">[[User:keithamus\|Keith Cirkel]]</span>		* <span class="h-card">[[User:keithamus\|Keith Cirkel]]</span>

			=== Web Machine Learning Community Group ===
			https://www.w3.org/groups/cg/webmachinelearning
			* <span class="h-card">Benjamin VanderSloot</span>

	== See Also ==		== See Also ==
	* [[Standards]]		* [[Standards]]
	* [[Standards/emeritus]] - past Mozilla participants in Community Groups		* [[Standards/emeritus]] - past Mozilla participants in Community Groups

Firefox/Channels/Meetings/2026-06-11

2026-06-11T15:13:10Z

Created page with " <center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | index | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center> '''Channel Meeting Details'..."

New page

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Thursdays at 7:30am Pacific Time
* Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings

'''Video/Teleconference Details'''
* Zoom Meeting ID: 536 097 768
* https://mozilla.zoom.us/j/536097768

{{Notes}}

__FORCETOC__

== Attendees ==
RyanVM, Mira, oardelean, gnichita, dbarladeanu, Aryx, jgibbs, dsmith, tzsoldos, btot, dveditz

== Schedule Update ==
* 151
** No updates.
* 152
** Desktop & Android 152.0b10 live on beta @ 100% rollout
** Desktop & Android 152 RC1 signed off by QA
*** Android Fenix/Focus 152.0 5% Play Store rollout to Production started
*** Will likely need an Android RC2 build to address bug 2046721 prior to ship
*** No Desktop respin driver at this time, but I’m watching bug 2038614 and bug 2046797
** ESR 140.12 & 115.37 pending release
** iOS Firefox/Focus 152.0 scheduled to start phased rollout at 03:00 UTC on 2026-06-14
** Firefox iOS 152.1 branches and Firefox iOS 152.1 gtb tomorrow
** Next week is Fx152 go-live on 2026-06-16
* 153
** String freeze starts tomorrow
** Merge Day and 153.0b1 build1 gtb next week on Monday 2026-06-15

== Release Quality Metrics ==
* https://bugdash.moz.tools/#tab.beta
** Nothing of concern. Most remaining issues are recently-reported sec bugs aiming for the mid-cycle dot release or low-severity carryover bugs.

== Desktop Stability ==
=== Nightly ===
crash incidence (% of users experiencing a crash): 2.90% (-0.32pp compared to previous week)
* no new frequent crashes

=== Beta ===
crash incidence: 1.80% (-0.24pp)
* no new frequent crashes

=== Release ===
crash incidence: 1.12% (-0.02pp)
* no new frequent crashes

== Mobile Stability ==

== QA ==
=== Nightly ===
* Nightly pre-merge testing is in progress. No concerns.
* Nightly search testing is in progress. No concerns.
=== Aurora / Dev Edition ===
=== Beta ===

=== Mobile ===
* Android / Mira
** Build Signoffs Fenix & Focus
*** Beta 152.0b8 - status GREEN
*** Beta 152.0b9 - status GREEN
*** RC 151.0.4 build 1 - status GREEN
*** Beta 152.0b10 - status GREEN
*** RC 152.0 - status YELLOW for Fenix, GREEN for Focus
** Feature Testing
*** [QA-5139] Android World Cup - Milestone 3 - Nightly 153 - status YELLOW
*** [QA-5139] Android World Cup - Milestone 3 - Beta 153 - status GREEN
*** [QA-5139] Android World Cup - Milestone 3 - 151.0.4 - status GREEN
*** [QA-5242] Native share sheet Android - Nightly 153 - status YELLOW
*** [QA-5256] LongFox Micro-game - Nightly 153 - status YELLOW
*** [QA-5308] Nova changes - bug verification in progress
*** [QA-5263] webgl web API changes - Nightly 153 testing in progress
*** [QA-5302] New paid marketing channels - spot check on 151.0.4 - complete
*** [QA-2799] Autofill webcompat testing (Austria, Switzerland, Mexico) - Beta 152 testing in progress
*** [QA-4980] Focus Nightly 153 - Android 17 - status GREEN
* iOS
** Build Signoffs
*** Focus iOS 151.3.1 (72936) - Release Candidate 1 - status [GREEN]
*** Firefox iOS 152.0 (73013) - Release Candidate 2 - status [GREEN]
** Feature Testing
*** [QA-5138] - iOS - World Cup Feature Milestone 4 - 152.0 RC testing finished -> Green status
*** [QA-5270] - Add categories to feed iOS - nightly testing in progress

== Action items ==

== Roundtable & Special Topics ==
* US holiday June 19

[[category:Channel_Meetings|{{SUBPAGENAME}}]]
[[Category:Wikipage templates]]

Release Management/Release Process Checklist Documentation

2026-06-11T14:48:33Z

The following tasks need to be performed 24 hours after go-live

← Older revision		Revision as of 14:48, 11 June 2026
(3 intermediate revisions by the same user not shown)
Line 694:		Line 694:
	# Email announce list		# Email announce list
	#* [https://groups.google.com/a/mozilla.org/g/release-signoff/c/p8y16VBG7EI/m/Y3d2w6pXAwAJ Example Email]		#* [https://groups.google.com/a/mozilla.org/g/release-signoff/c/p8y16VBG7EI/m/Y3d2w6pXAwAJ Example Email]
	~~# Schedule Desktop update rate to 0% in [https://balrog.services.mozilla.com/rules?product=Firefox&channel=release Balrog] after 24 hours.~~
	~~# Signoff on scheduled rule change in Balrog.~~
	~~#* Sync with release management for another team member to signoff on the rule change.~~

	==The following tasks need to be performed 24 hours after go-live==		==The following tasks need to be performed 24 hours after go-live==
	# ~~Verify~~ Desktop update rate at 0% in [https://balrog.services.mozilla.com/rules?product=Firefox&channel=release Balrog]		# Review release crash rates and incoming bugs for new blockers.
	~~# Email release-signoff & release-drivers to confirm 0~~% ~~throttling.~~		#* Only change Desktop update rate to 0% in [https://balrog.services.mozilla.com/rules?product=Firefox&channel=release Balrog]if something is critical, otherwise maintain the rate at 25% for another 24 hours.
	~~#* Reply to the previous email from the go-live day~~.
	~~#* [https://groups.google.com/a/mozilla.org/g/release-signoff/c/p8y16VBG7EI/m/dyJYXwamAwAJ Example Email]~~

	==The following tasks need to be performed 48 hours after go-live==		==The following tasks need to be performed 48 hours after go-live==

Support/Weekly Meetings/Agenda 2026-06-17

2026-06-11T10:38:48Z

Event discussions & questions: thread for June

← Older revision		Revision as of 10:38, 11 June 2026
(One intermediate revision by the same user not shown)
Line 14:		Line 14:

	=== Event discussions & questions ===		=== Event discussions & questions ===
	* [https://support.mozilla.org/forums/contributors/ Community discussion thread]		* [https://support.mozilla.org/forums/contributors/717663 Community discussion thread]

	=== Attendance and live chat ===		=== Attendance and live chat ===
Line 32:		Line 32:

	== AGENDA ==		== AGENDA ==
	Slides are available [https://docs.google.com/presentation/ here].		<!-- Slides are available [https://docs.google.com/presentation/ here]. -->
	=== TOPIC OF THE MONTH ===		=== TOPIC OF THE MONTH ===
	# Firefox widgets - Amber Meryman		# Firefox widgets - Amber Meryman

User:SpikeUK1

2026-06-11T08:01:25Z

Account approvals : June 2026: Six from likely spammer rejected. Zero backlog.

← Older revision		Revision as of 08:01, 11 June 2026
(One intermediate revision by the same user not shown)
Line 255:		Line 255:
	\| 9<sup>th</sup> June 2026 \|\| 0 \|\| 10 \|\| 0 \|\| 0 \|\| 10		\| 9<sup>th</sup> June 2026 \|\| 0 \|\| 10 \|\| 0 \|\| 0 \|\| 10
	\|-		\|-
	\| 10<sup>th</sup> June 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7		\| 10<sup>th</sup> June 2026 \|\| 0 \|\| 12 \|\| 0 \|\| 0 \|\| 12
			\|-
			\| 11<sup>th</sup> June 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6
	\|}		\|}

Support/Weekly Meetings/Agenda 2026-06-17

2026-06-10T10:08:35Z

placeholder for June 2026

New page

== Meeting Details (scroll down for the agenda) ==
(meeting duration approx. 45 minutes) starting at: '''18:00 UTC''' (click [http://www.thetimezoneconverter.com/?t=18:00&tz=UTC& here] to convert the schedule to your timezone)

=== Participate ===
First time joining the call? Check out [https://support.mozilla.org/kb/how-participate-sumo-contributor-meetings this guide] to learn more about how to participate.

==== Join us live ====
* You can participate live by joining us on [https://mozilla.zoom.us/j/490084542 Zoom]. There are also free Zoom backgrounds you can download [https://drive.google.com/drive/folders/1HhUnYh6pnp--pBBmX21uavlBHnsVL2yn?usp=drive_link here].

==== Watch the livestream ====
You can choose to watch the livestream from the following platforms:
* [https://mzl.la/sumo-2026-06-17 Air Mozilla]
* [https://youtube.com/live YouTube] (Set a reminder on YouTube)

=== Event discussions & questions ===
* [https://support.mozilla.org/forums/contributors/ Community discussion thread]

=== Attendance and live chat ===
* [https://chat.mozilla.org/#/room/#SUMO:mozilla.org Matrix] - Please use it for back-channel during the call
* [https://community.mozilla.org/en/events/community-call-may-2026/ Meeting attendance] (Click attend if you join us or watch the livestream)

=== Learn more about us ===
* [http://blog.mozilla.org/sumo Mozilla Support blog]
* [http://blog.mozilla.org/community Mozilla Community blog]
* [https://support.mozilla.org/forums Contributor Discussions]

-----------------------------------------------------------------------------------------------------------------------------

== Hosts, guests, and participants ==
* [https://support.mozilla.org/user/kelimuttu/ Kiki] - Community Manager
*

== AGENDA ==
Slides are available [https://docs.google.com/presentation/ here].
=== TOPIC OF THE MONTH ===
# Firefox widgets - Amber Meryman
# Old sidebar deprecation - Ania Safko

=== PRODUCT UPDATE ===
#
#
#

=== COMMUNITY'S UPDATE ===
#
#
#

=== EVENT'S FEEDBACK FORM ===
Share what you want to hear from us next by taking [https://mzl.la/moz-call-feedback our feedback form]. Thanks for attending!

==== WRITTEN UPDATE ====
#

User:SpikeUK1

2026-06-10T06:53:12Z

Account approvals : June 2026: Seven from likely spammer rejected. Zero backlog.

← Older revision		Revision as of 06:53, 10 June 2026
Line 254:		Line 254:
	\|-		\|-
	\| 9<sup>th</sup> June 2026 \|\| 0 \|\| 10 \|\| 0 \|\| 0 \|\| 10		\| 9<sup>th</sup> June 2026 \|\| 0 \|\| 10 \|\| 0 \|\| 0 \|\| 10
			\|-
			\| 10<sup>th</sup> June 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7
	\|}		\|}

Template:FIREFOX RELEASE DATE

2026-06-10T06:48:21Z

Correct

← Older revision		Revision as of 06:48, 10 June 2026
Line 542:		Line 542:
	\| 151.0.2 = 2026-05-25		\| 151.0.2 = 2026-05-25
	\| 151.0.3 = 2026-06-01		\| 151.0.3 = 2026-06-01
	\| 151.0.3 = 2026-06-08		\| 151.0.4 = 2026-06-08
	\| 152.0 = 2026-06-16		\| 152.0 = 2026-06-16
	\| 153.0 = 2026-07-21		\| 153.0 = 2026-07-21

Template:Version/Firefox/release/current

2026-06-10T06:47:17Z

Update Firefox version from 151.0.3 to 151.0.4

← Older revision		Revision as of 06:47, 10 June 2026
Line 1:		Line 1:
	151.0.3		151.0.4

Template:FIREFOX RELEASE DATE

2026-06-10T06:46:35Z

Add Firefox version 151.0.4 = 2026-06-08

← Older revision		Revision as of 06:46, 10 June 2026
Line 542:		Line 542:
	\| 151.0.2 = 2026-05-25		\| 151.0.2 = 2026-05-25
	\| 151.0.3 = 2026-06-01		\| 151.0.3 = 2026-06-01
			\| 151.0.3 = 2026-06-08
	\| 152.0 = 2026-06-16		\| 152.0 = 2026-06-16
	\| 153.0 = 2026-07-21		\| 153.0 = 2026-07-21

Support/Firefox151

2026-06-10T05:12:14Z

Known incidents: align formatting

← Older revision		Revision as of 05:12, 10 June 2026
(3 intermediate revisions by the same user not shown)
Line 26:		Line 26:
	\|-		\|-
	\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.1/releasenotes/ 151.0.1] \|\| May 21, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=1950764 bug1950764], [https://bugzilla.mozilla.org/show_bug.cgi?id=2040754 bug2040754] \|\| -		\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.1/releasenotes/ 151.0.1] \|\| May 21, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=1950764 bug1950764], [https://bugzilla.mozilla.org/show_bug.cgi?id=2040754 bug2040754] \|\| -
			\|-
			\| Firefox for Android \|\| [https://www.mozilla.org/firefox/android/151.0.1/releasenotes/ 151.0.1] \|\| May 26, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2041355 bug 2041355] \|\| -
	\|-		\|-
	\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.2/releasenotes/ 151.0.2] \|\| May 26, 2026 \|\| Various bug fixes \|\| -		\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.2/releasenotes/ 151.0.2] \|\| May 26, 2026 \|\| Various bug fixes \|\| -
	\|-
	~~\| Firefox for Android \|\| [https://www.mozilla.org/firefox/android/151.0.1/releasenotes/ 151.0.1] \|\| May 26, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2041355 bug 2041355] \|\| -~~
	\|-		\|-
	\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.3/releasenotes/ 151.0.3] \|\| June 2, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2041235 bug2041235], [https://bugzilla.mozilla.org/show_bug.cgi?id=2042454 bug2042454], and various [https://www.mozilla.org/en-US/security/advisories/mfsa2026-54/ security fixes] \|\| -		\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.3/releasenotes/ 151.0.3] \|\| June 2, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2041235 bug2041235], [https://bugzilla.mozilla.org/show_bug.cgi?id=2042454 bug2042454], and various [https://www.mozilla.org/en-US/security/advisories/mfsa2026-54/ security fixes] \|\| -
	\|-		\|-
	\| Firefox for Android \|\| [https://www.mozilla.org/firefox/android/151.0.3/releasenotes/ 151.0.3] \|\| June 2, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2042018 bug2042018], [https://bugzilla.mozilla.org/show_bug.cgi?id=2038467 bug2038467], and various [https://www.mozilla.org/en-US/security/advisories/mfsa2026-54/ security fixes] \|\| -		\| Firefox for Android \|\| [https://www.mozilla.org/firefox/android/151.0.3/releasenotes/ 151.0.3] \|\| June 2, 2026 \|\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2042018 bug2042018], [https://bugzilla.mozilla.org/show_bug.cgi?id=2038467 bug2038467], and various [https://www.mozilla.org/en-US/security/advisories/mfsa2026-54/ security fixes] \|\| -
			\|-
			\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/151.0.4/releasenotes/ 151.0.4] \|\| June 9, 2026 \|\| Various bug fixes \|\| -
			\|-
			\| Firefox for Android \|\| [https://www.mozilla.org/firefox/android/151.0.4/releasenotes/ 151.0.4] \|\| June 9, 2026 \|\| World Cup widget\|\| -
	<!--		<!--
	\|-		\|-
Line 317:		Line 321:
	\|'''Resolution/workaround:'''		\|'''Resolution/workaround:'''
	\| The Nimbus experiment has been fixed		\| The Nimbus experiment has been fixed
			\|}

			{\| class="wikitable"
			!colspan="2"\| Smartcard certificates not loading in Firefox 151
			\|-
			\|'''Description:'''
			\| Smartcard certificates are not loaded in MacOS 26.5 since Firefox 151
			\|-
			\|'''Status:'''
			\| Resolved
			\|-
			\|'''Product(s) impacted:'''
			\| Firefox Desktop
			\|-
			\|'''Associated bug:'''
			\| [https://bugzilla.mozilla.org/show_bug.cgi?id=2041093 bug2041093]
			\|-
			\|'''Resolution/workaround:'''
			\| Fixed with the release of 151.0.2
	\|}		\|}
	<!--		<!--

Events

2026-06-09T20:53:17Z

2023: dates for reclaim

← Older revision		Revision as of 20:53, 9 June 2026
(One intermediate revision by the same user not shown)
Line 82:		Line 82:

	== 2023 ==		== 2023 ==
			=== October 2023 ===
			* 2023-10-12…16 [https://reimagine.mozilla.org/ Reclaim the Internet – Reimagining Our Digital Future] in Alte Münze, Berlin, Germany
	=== August 2023 ===		=== August 2023 ===
	* [[All Hands]] in Montreal		* [[All Hands]] in Montreal, Canada

	== 2022 ==		== 2022 ==

Rise25

2026-06-09T20:24:13Z

stub with 2024 and 2023 events, dates, locations, links to more info, video

New page

{{stub}}

'''<dfn>[https://rise25.mozilla.org/ Rise25]</dfn>''' was an annual recognition of 25 people who are "are leading that next wave of AI" from 2023-2024.

== 2024 ==
The 2025 Rise25 Awards was held during the 2024 [[MozWeek]] event in Dublin, Ireland.

Nominations:
* https://www.mozilla.org/en-US/rise25/nominate/ was used to nominate candidates for the awards.
* https://blog.mozilla.org/en/mozilla/mozilla-rise25-ai-nominations/

== 2023 ==
The 2023 Rise25 Awards was held on Friday October 13, during the [https://reimagine.mozilla.org/en Reclaim the internet event] October 12—16, 2023 in Berlin, Germany.
* https://blog.mozilla.org/en/mozilla/rise-25-winners/
* https://blog.mozilla.org/en/internet-culture/trisha-prabhu-rise25-rethink-cyberbullying/
* Videos: https://www.youtube.com/playlist?list=PLnRGhgZaGeBs96fHlOFhrVaHsgflAX4cP

Allhands

2026-06-09T20:21:01Z

redirect generic top level term to same place as All Hands for easier discovery

← Older revision		Revision as of 20:21, 9 June 2026
Line 1:		Line 1:
	~~https://dl.dropboxusercontent.com/spa/7qmeizr99t5swur/hn8lcoej.png~~		#REDIRECT [[MozWeek#Prior_All_Hands_Events]]

MozWeek/2016 London

2026-06-09T20:19:28Z

add see also with a couple of links recovered from Allhands history

← Older revision		Revision as of 20:19, 9 June 2026
Line 498:		Line 498:
	Ask your general questions until June 1 [https://docs.google.com/document/d/15lnuJH9U6W0QvKoBf17rVsw1vQp3p6VWjqwmneenPu8/edit?usp=sharing here] or email bmark@ for questions specific to you.		Ask your general questions until June 1 [https://docs.google.com/document/d/15lnuJH9U6W0QvKoBf17rVsw1vQp3p6VWjqwmneenPu8/edit?usp=sharing here] or email bmark@ for questions specific to you.
	Volunteers may refer [https://discourse.mozilla-community.org/t/all-hands-faq-london-workweek/7995 this FAQ]		Volunteers may refer [https://discourse.mozilla-community.org/t/all-hands-faq-london-workweek/7995 this FAQ]

			== See Also ==
			Links related to this event gathered from other sources:
			* 2016 London session proposals were made at: http://mzl.la/github_sessions
			* 2016 London MoFo schedule in progress: http://mzl.la/sched_spreadsheet

User:Matt Thompson

2026-06-09T20:19:14Z

fix blog link typo

← Older revision		Revision as of 20:19, 9 June 2026
Line 2:		Line 2:

	Email: matt@mozillafoundation.org<br>		Email: matt@mozillafoundation.org<br>
	[http://openmatt.~~orga~~ Blog]<br>		[http://openmatt.org Blog]<br>
	[http://twitter.com/OpenMatt Twitter]<br>		[http://twitter.com/OpenMatt Twitter]<br>
	[http://www.facebook.com/#!/profile.php?id=559640845 Facebook]<br>		[http://www.facebook.com/#!/profile.php?id=559640845 Facebook]<br>

BMO/Recent Changes/2026-06

2026-06-09T17:03:28Z

Created page with "== 2026-06-09 == [https://github.com/mozilla-bteam/bmo/tree/release-20260609.1 release-20260609.1] * {{bug|2043429}} Selenium test 1_test_bug_edit.t intermittently fails when attemtping to click on comment reactions * {{bug|1995467}} Show dependency tree on meta bugs by default * {{bug|2043322}} text/html attachments are downloaded instead of viewing in-browser * {{bug|2038298}} Render Phabricator revisions stack fork in the parent's row * {{bug|2045855}} phab-bot atte..."

New page

== 2026-06-09 ==

[https://github.com/mozilla-bteam/bmo/tree/release-20260609.1 release-20260609.1]
* {{bug|2043429}} Selenium test 1_test_bug_edit.t intermittently fails when attemtping to click on comment reactions
* {{bug|1995467}} Show dependency tree on meta bugs by default
* {{bug|2043322}} text/html attachments are downloaded instead of viewing in-browser
* {{bug|2038298}} Render Phabricator revisions stack fork in the parent's row
* {{bug|2045855}} phab-bot attempts to set approval flags for disabled flags
* {{bug|2044471}} Add loading indicator to embedded dependency tree
* {{bug|2034031}}

Security Severity Ratings/Client

2026-06-09T17:03:23Z

csectype- Keywords: adding csectype-site-isolation

← Older revision		Revision as of 17:03, 9 June 2026
Line 167:		Line 167:
	\|-		\|-
	\|csectype-side-channel \|\| Disclosure of sensitive information or state through side-effects (typically, timing)		\|csectype-side-channel \|\| Disclosure of sensitive information or state through side-effects (typically, timing)
			\|-
			\|csectype-site-isolation \|\| client security issues in limiting content processes to data and settings for a single site. distinct from web content csectype-sop and non-site-to-site csectype-priv-escalation
	\|-		\|-
	\|csectype-sop \|\| violations of the client Same Origin Policy including Universal-XSS (see also csectype-side-channel for less severe "leaks")		\|csectype-sop \|\| violations of the client Same Origin Policy including Universal-XSS (see also csectype-side-channel for less severe "leaks")

BMO/Recent Changes

2026-06-09T17:03:10Z

Security/Firefox/Security Bug Life Cycle/Security Advisories

2026-06-09T13:47:34Z

explain cve assignment by github action

← Older revision		Revision as of 13:47, 9 June 2026
Line 27:		Line 27:
	Have your main reviewer do the following (because it requires CVE credentials):		Have your main reviewer do the following (because it requires CVE credentials):
	# Set up CVE and Bugzilla credentials, (maybe try <code>DRY_RUN=1</code>)		# Set up CVE and Bugzilla credentials, (maybe try <code>DRY_RUN=1</code>)
	# Run <code>assign_cve_ids</code>, this should reserve IDs and set the alias of each bug in Bugzilla to its CVE ID. See [[#Assign_CVEs]] for more.		# Run <code>assign_cve_ids</code>, this should reserve IDs and set the alias of each bug in Bugzilla to its CVE ID. See [[#Assign_CVEs]] for more. If you omit this step the GitHub action will assign the CVEs but it does not have access to Bugzilla so it will not set the aliases.
	Then follow up with release managers to merge your PR.		Then follow up with release managers to merge your PR.

Line 88:		Line 88:
	Typically done a day or two before the release, assign CVEs to the bugs in bugzilla and in the yml file. This needs to be done by a person with CVE Services credentials and Bugzilla security access, and can be automated with the '''assign_cve_ids''' script in the [https://github.com/mozilla/foundation-security-advisories foundation-security-advisories] repository.		Typically done a day or two before the release, assign CVEs to the bugs in bugzilla and in the yml file. This needs to be done by a person with CVE Services credentials and Bugzilla security access, and can be automated with the '''assign_cve_ids''' script in the [https://github.com/mozilla/foundation-security-advisories foundation-security-advisories] repository.

	That script will automatically reserve new CVEs, insert them into the yml file, and set the CVE IDs as aliases on Bugzilla. You can use it by running <tt>pip i && assign_cve_ids</tt> in the root of the repository. You can provide the required credentials through the '''CVE_USER''', '''CVE_ORG''', '''CVE_API_KEY''', '''CVE_ENV''', and '''BUGZILLA_API_KEY''' environment variables. Before running the script, make sure to set the names of the advisories that should get a CVE ID to '''MFSA-RESERVE-{YEAR}-{BUG_ID}''', where '''{YEAR}''' is the year that should be associated with the CVE, and '''{BUG_ID}''' is the id of a Bugzilla bug that should get the CVE ID as an alias. If you do not want to have a alias set for the advisory, use a small unique number instead. If you have used the [[#Generate_and_edit_the_YML_File\|'''gen_yml.py''' script from the previous step]] to generate your yml file, the advisories should already have this format.		That script will automatically reserve new CVEs, insert them into the yml file, and set the CVE IDs as aliases on Bugzilla. You can use it by running <tt>pip i && assign_cve_ids</tt> in the root of the repository. You can provide the required credentials through the '''CVE_USER''', '''CVE_ORG''', '''CVE_API_KEY''', '''CVE_ENV''', and '''BUGZILLA_API_KEY''' environment variables. Before running the script, make sure to set the names of the advisories that should get a CVE ID to '''MFSA-RESERVE-{YEAR}-{BUG_ID}''', where '''{YEAR}''' is the year that should be associated with the CVE, and '''{BUG_ID}''' is the id of a Bugzilla bug that should get the CVE ID as an alias. If you do not want to have a alias set for the advisory, use a small unique number instead. If you have used the [[#Generate_and_edit_the_YML_File\|'''gen_yml.py''' script from the previous step]] to generate your yml file, the advisories should already have this format. If you omit this step the GitHub action will assign the CVEs but it does not have access to Bugzilla so it will not set the aliases.

	A noteworthy item is that '''issues that already have had a CVE assigned''' - for example because it's an upstream bug - should instead have their identifier set to that CVE. If the issue should have a CVE from another org but we don't have it yet, then it should be set to '''MFSA-TMP-2025-XXXX''' where XXXX is an incrementing number. We strive not to re-ruse these. It is common (usually once or twice a year) for us to request Google to assign a CVE for an issue in an upstream library. The Googler to contact for this is James Zern, and Tom Ritter (among others) can put you in touch.		A noteworthy item is that '''issues that already have had a CVE assigned''' - for example because it's an upstream bug - should instead have their identifier set to that CVE. If the issue should have a CVE from another org but we don't have it yet, then it should be set to '''MFSA-TMP-2025-XXXX''' where XXXX is an incrementing number. We strive not to re-ruse these. It is common (usually once or twice a year) for us to request Google to assign a CVE for an issue in an upstream library. The Googler to contact for this is James Zern, and Tom Ritter (among others) can put you in touch.

User:SpikeUK1

2026-06-09T09:16:54Z

Account approvals : June 2026: Ten from likely spammer rejected. Zero backlog.

← Older revision		Revision as of 09:16, 9 June 2026
Line 252:		Line 252:
	\|-		\|-
	\| 8<sup>th</sup> June 2026 \|\| 0 \|\| 36 \|\| 0 \|\| 0 \|\| 36		\| 8<sup>th</sup> June 2026 \|\| 0 \|\| 36 \|\| 0 \|\| 0 \|\| 36
			\|-
			\| 9<sup>th</sup> June 2026 \|\| 0 \|\| 10 \|\| 0 \|\| 0 \|\| 10
	\|}		\|}

SeaMonkey/StatusMeetings

2026-06-09T02:47:12Z

added link to 2026-06-21 page

← Older revision		Revision as of 02:47, 9 June 2026
Line 11:		Line 11:

	'''Meeting Notes (agendas + minutes)'''		'''Meeting Notes (agendas + minutes)'''
			* [[SeaMonkey/StatusMeetings/2026-06-21\|June 21, 2026]]
	* [[SeaMonkey/StatusMeetings/2026-05-31\|May 31, 2026]]		* [[SeaMonkey/StatusMeetings/2026-05-31\|May 31, 2026]]
	* [[SeaMonkey/StatusMeetings/2026-05-10\|May 10, 2026]]		* [[SeaMonkey/StatusMeetings/2026-05-10\|May 10, 2026]]

SeaMonkey/StatusMeetings/2026-06-21

2026-06-09T02:45:29Z

copied from 2026-05-31 minutes

Show changes

MozPhab/Changelog

2026-06-08T18:31:20Z

add 2.15.2 release notes

← Older revision		Revision as of 18:31, 8 June 2026
Line 1:		Line 1:
	== Changelog ==		== Changelog ==

			=== 2.15.2 ===
			* {{bug\|2004368}} moz-phab patch -a here with jj says there is no source tree if jj config is broken
			* {{bug\|2035900}} Investigate setting up CodSpeed.io for `moz-phab`
			* {{bug\|2044857}} `patch --raw` leaks a global logger level, causing order-dependent test failures

	=== 2.15.1 ===		=== 2.15.1 ===

Privacy/Docs

2026-06-08T17:40:22Z

Github repository: add firefox-privacy-prefs

← Older revision		Revision as of 17:40, 8 June 2026
Line 52:		Line 52:
	** https://github.com/mozilla/anti-tracking-test-pages		** https://github.com/mozilla/anti-tracking-test-pages
	** https://github.com/mozilla/cookie-banner-rules-list (archived)		** https://github.com/mozilla/cookie-banner-rules-list (archived)
			** https://github.com/mozilla/firefox-privacy-prefs (for https://firefox-source-docs.mozilla.org/toolkit/components/antitracking/anti-tracking/etp-matrix/index.html)
	** https://github.com/mozilla/url-classifier-exceptions-creation (archived)		** https://github.com/mozilla/url-classifier-exceptions-creation (archived)
	** https://github.com/mozilla/url-classifier-exceptions-manager (Bugzilla: [https://bugzilla.mozilla.org/user_profile?user_id=778243 privacy-bot@bmo.tld])		** https://github.com/mozilla/url-classifier-exceptions-manager (Bugzilla: [https://bugzilla.mozilla.org/user_profile?user_id=778243 privacy-bot@bmo.tld])

Release Management/Release Process Checklist Documentation

2026-06-08T17:12:14Z

update beta->release dry run documentation

← Older revision		Revision as of 17:12, 8 June 2026
Line 433:		Line 433:

	==The following needs to be performed at the end of the Beta Cycle==		==The following needs to be performed at the end of the Beta Cycle==
	# ~~Verfiy the automated~~ mozilla-beta->mozilla-release migration ~~no-op trial~~ run		# Schedule a mozilla-beta->mozilla-release migration dry run
	#* The job ~~automatically runs every Friday and the link is shared on the [https://matrix.to/#/#releaseduty:mozilla.org #release~~-~~duty] channel in Matrix~~.		#* The job can be scheduled in Ship-It from "Merge Automation > Firefox Desktop".
	#* See [https://moz-releng-docs.readthedocs.io/en/latest/how-to/releaseduty/merge-duty/merge_duty.html#mozilla-beta-mozilla-release-migration-no-op-trial-run #do-migration-no-op-trial-runs] for documentation.		#* Verify the resulting diffs created by the graph.
	# Disable automated beta builds in Ship-it.		# Disable automated beta builds in Ship-it.
	# Please Note: Monitor beta/release uplift requests between the final beta build and the beta to release merge. It is possible that a late uplift request may come in for a regression/stability fix, evaluate if this is a blocker for the RC and if it should be uplifted to beta before the beta to release merge and RC build.		# Please Note: Monitor beta/release uplift requests between the final beta build and the beta to release merge. It is possible that a late uplift request may come in for a regression/stability fix, evaluate if this is a blocker for the RC and if it should be uplifted to beta before the beta to release merge and RC build.


	=iOS XXX.0 Checklist=		=iOS XXX.0 Checklist=

User:SpikeUK1

2026-06-08T15:28:04Z

Account approvals : June 2026: Sixteen more from likely spammer rejected. Zero backlog.

← Older revision		Revision as of 15:28, 8 June 2026
(2 intermediate revisions by the same user not shown)
Line 248:		Line 248:
	\|-		\|-
	\| 4<sup>th</sup> June 2026 \|\| 0 \|\| 12 \|\| 0 \|\| 0 \|\| 12		\| 4<sup>th</sup> June 2026 \|\| 0 \|\| 12 \|\| 0 \|\| 0 \|\| 12
			\|-
			\| 5<sup>th</sup> June 2026 \|\| 0 \|\| 4 \|\| 0 \|\| 0 \|\| 4
			\|-
			\| 8<sup>th</sup> June 2026 \|\| 0 \|\| 36 \|\| 0 \|\| 0 \|\| 36
	\|}		\|}

← Older revision		Revision as of 17:03, 9 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	= Recent Changes =		= Recent Changes =

			== 2026-06-09 ==

			[https://github.com/mozilla-bteam/bmo/tree/release-20260609.1 release-20260609.1]
			* {{bug\|2043429}} Selenium test 1_test_bug_edit.t intermittently fails when attemtping to click on comment reactions
			* {{bug\|1995467}} Show dependency tree on meta bugs by default
			* {{bug\|2043322}} text/html attachments are downloaded instead of viewing in-browser
			* {{bug\|2038298}} Render Phabricator revisions stack fork in the parent's row
			* {{bug\|2045855}} phab-bot attempts to set approval flags for disabled flags
			* {{bug\|2044471}} Add loading indicator to embedded dependency tree
			* {{bug\|2034031}}

	== 2026-05-27 ==		== 2026-05-27 ==
Line 31:		Line 42:
	* {{bug\|2033979}}		* {{bug\|2033979}}
	* {{bug\|2036552}}		* {{bug\|2036552}}

	~~== 2026-04-28 ==~~

	~~[https://github.com/mozilla-bteam/bmo/tree/release-20260428.1 release-20260428.1]~~
	* {{bug\|2034051}} Update Bugzilla Etiquette with guidance about AI usage
	* {{bug\|2033409}} Pasting a link from the clipboard after using the Link button inserts additional markdown into the link
	* {{bug\|2034240}} Need to remove the link to Mozilla Gear from custom_forms.html.tmpl as it was left over from previous removals
	* {{bug\|2035387}} Unable to file MDN security bugs - `file error - cannot find file - bug/create/create-mdn.html.tmpl ()`

	= Archive =		= Archive =

			* [[BMO/Recent_Changes/2026-06\|2026-06]]
	* [[BMO/Recent_Changes/2026-05\|2026-05]]		* [[BMO/Recent_Changes/2026-05\|2026-05]]
	* [[BMO/Recent_Changes/2026-04\|2026-04]]		* [[BMO/Recent_Changes/2026-04\|2026-04]]