-
== DEER PARK PRODUCT PLANNING AND RELEASE MANAGEMENT ==
''(Deer Park is the code name for the next release of Mozilla Firefox.)''
12 KB (1,587 words) - 02:58, 14 October 2009
-
...leases/Firefox_21/Test_Plan|Firefox 21]] | [[Releases/Firefox_22/Test_Plan|Firefox 22 ยป]] </small>
= Firefox 21 Test Plan =
137 KB (18,121 words) - 09:33, 5 February 2014
-
...ocumentation Lead (DL) roles. Use the checklist to track the status of the release.
==Past SDK Release checklists==
23 KB (3,610 words) - 09:19, 20 March 2013
-
==== 2.40.1 release ====
* Doing a 2.40.1 release was suggested until 2.46 is ready because of the 0-day bug.
40 KB (6,045 words) - 23:28, 7 January 2017
-
...lopment build will be automatically updated to the new build the next time Firefox checks for updates.
== Stable Release Build ==
9 KB (1,390 words) - 22:51, 14 December 2009
-
** '''ewong for quick 2.53.5.1 release uploading and WolfiR for bringing SM up-to-date in openSUSE releases'''
=== Status of the SeaMonkey Infrastructure ===
35 KB (5,254 words) - 14:04, 13 December 2020
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
40 KB (6,094 words) - 20:59, 1 September 2019
-
=== Status of the SeaMonkey infrastructure ===
...ore updates to the old infrastructure nor will there be any reports on the status of the old buildbot master.
32 KB (4,793 words) - 21:34, 22 July 2018
-
** '''TPR75 for testing SeaMonkey candidate builds'''
=== Status of the SeaMonkey Infrastructure ===
34 KB (5,181 words) - 10:18, 6 July 2019
-
==== Release Planning next release ====
...next SeaMonkey release. This would mean SeaMonkey 2.49 will become an ESR release still providing Windows XP and Vista compatibility.
36 KB (5,341 words) - 11:06, 24 January 2017
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
35 KB (5,396 words) - 20:03, 21 July 2019
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
36 KB (5,379 words) - 19:05, 9 August 2020
-
* Mozilla plans to check in l20n early in the Firefox 53 release cycle. Unclear what this means for comm-central and the build configs. Need
* Google announced V4 of the safebrowsing api. No actions currently needed. Firefox adds support for it in {{bug|1167038}}.
33 KB (4,926 words) - 21:06, 8 November 2016
-
* Mozilla plans to check in l20n early in the Firefox 53 release cycle. Unclear what this means for comm-central and the build configs. Need
* Google announced V4 of the safebrowsing api. No actions currently needed. Firefox adds support for it in {{bug|1167038}}.
34 KB (5,016 words) - 17:33, 4 December 2016
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
32 KB (4,850 words) - 22:50, 19 November 2020
-
** '''ewong frg IanN WG9s for the 2.53.3 release and daily builds'''
* Status flags for 2.49esr need to be removed for new SeaMonkey bugs (completed, {{B
35 KB (5,245 words) - 18:12, 13 July 2020
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
34 KB (5,104 words) - 19:17, 21 September 2020
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
35 KB (5,423 words) - 23:32, 11 August 2019
-
Firefox 29 has shipped, and thus ends our weekly Australis meetings! So long and th
* Post-release!
200 KB (31,637 words) - 00:20, 8 May 2014
-
=== Status of the SeaMonkey Infrastructure ===
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
34 KB (5,204 words) - 16:01, 9 August 2020
