You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change updates the documentation to account for the source code
moving from Mercurial to Git.
The following sections still need updating:
* The try build steps need updating once we switch to `./mach try`
thunderbird-development/fixing-a-bug/try-server.md
* Landing a patch
thunderbird-development/fixing-a-bug/landing-a-patch.md
Closes#239
Copy file name to clipboardExpand all lines: add-ons/mailextensions/experiments.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,12 @@ Since Experiments directly interact with Thunderbird's core functions, it is nec
7
7
{% endhint %}
8
8
9
9
{% hint style="info" %}
10
-
Thunderbird does contain a few useful features related to Experiments [whose documentation is no longer generated](https://bugzilla.mozilla.org/show\_bug.cgi?id=1556460#c23). Especially if you're writing an Experiment with complex interactions between the WebExtension and your Experiment, it may be helpful to read the documentation blocks within [ExtensionCommon.sys.mjs](https://searchfox.org/mozilla-central/source/toolkit/components/extensions/ExtensionCommon.sys.mjs) and possibly other modules in the same source code folder.
10
+
Thunderbird does contain a few useful features related to Experiments [whose documentation is no longer generated](https://bugzilla.mozilla.org/show\_bug.cgi?id=1556460#c23). Especially if you're writing an Experiment with complex interactions between the WebExtension and your Experiment, it may be helpful to read the documentation blocks within [ExtensionCommon.sys.mjs](https://github.com/mozilla-firefox/firefox/blob/main/toolkit/components/extensions/ExtensionCommon.sys.mjs) and possibly other modules in the same source code folder.
11
11
{% endhint %}
12
12
13
13
{% hint style="info" %}
14
14
For reference, the parent implementations of all built-in APIs can be found in\
|[Searchfox](https://searchfox.org/)| An online viewer to search the Firefox code base ([_mozilla-central_](https://searchfox.org/mozilla-central/source/)) and the Thunderbird code base ([_comm-central_](https://searchfox.org/comm-central/source/)). |
32
+
|[Searchfox](https://searchfox.org/)| An online viewer to search the Firefox code base ([_mozilla-central_](https://github.com/mozilla-firefox/firefox/blob/main/)) and the Thunderbird code base ([_comm-central_](https://github.com/thunderbird/thunderbird-desktop/blob/main/)). |
33
33
|[Firefox Source Tree documentation](https://firefox-source-docs.mozilla.org/)| The current Firefox code documentation, which might be needed when converting legacy extensions. |
34
34
|[Thunderbird Source Tree documentation](../../thunderbird-development/codebase-overview/)| The current Thunderbird code documentation, in addition to comments in [idl files on comm-central](https://searchfox.org/comm-central/search?q=\&path=\*.idl). This is still work in progress. |
35
35
|[Archived XUL and XPCOM Documentation](https://udn.realityripple.com/docs/Mozilla)| <p>The archived Mozilla documentation includes information about internal components and functions used by legacy extensions. Please be aware, that those pages are not maintained and are potentially outdated. Some useful direct links:</p><ul><li><ahref="https://udn.realityripple.com/docs/Mozilla/JavaScript_code_modules">Archived JavaScript Code Modules</a></li><li><ahref="https://udn.realityripple.com/docs/Archive/Mozilla/XUL">Archived XUL Documentation</a></li><li><ahref="https://udn.realityripple.com/docs/Mozilla/Tech/XPCOM/Reference/Interface">Archived XPCOM Interface Reference</a></li></ul> |
Copy file name to clipboardExpand all lines: add-ons/updating/tb102/adapt-to-changes-in-thunderbird-92-102.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ The method to retrieve strings from the created bundle is slightly different, in
81
81
82
82
### calICalendar.\*
83
83
84
-
Since Thunderbird 96, [many calendar functions return Promises](https://searchfox.org/comm-central/source/calendar/base/public/calICalendar.idl). This includes:
84
+
Since Thunderbird 96, [many calendar functions return Promises](https://github.com/thunderbird/thunderbird-desktop/blob/main/calendar/base/public/calICalendar.idl). This includes:
The following list also includes deprecated elements, which could still be used but Thunderbird has already started to purge their usage. In that case you must update your overlay files which are overlaying such elements, otherwise your overlay will not be applied. Check [SearchFox](https://searchfox.org/comm-central/source) for the current state of the files you are overlaying.
58
+
The following list also includes deprecated elements, which could still be used but Thunderbird has already started to purge their usage. In that case you must update your overlay files which are overlaying such elements, otherwise your overlay will not be applied. Check [SearchFox](https://github.com/thunderbird/thunderbird-desktop/blob/main) for the current state of the files you are overlaying.
59
59
60
60
{% hint style="info" %}
61
61
The replacements listed here might work in subtly different ways. Check your functionality!
@@ -217,5 +217,5 @@ In Thunderbird 91, this is primarily affecting pages belonging to an Add-on, lik
217
217
In practical terms, this means that you may need to update your experiments:
218
218
219
219
***If you create frames in Thunderbird's UI**, these frames now need the appropriate attributes to load content in the right process. You can find an example of required changes in [the E10S compatibility commit for the CustomUI experiment](https://github.com/rsjtdrjgfuzkfg/thunderbird-experiments/commit/11232201ff437e7bb293efdcb93ecc3963a8328d#diff-41cf834ce8c3fae411d5f4c18abf8c024630074e616cf98307e582cea5362be7).
220
-
***If you exchange raw objects between WebExtension scopes / "child" experiment code and Thunderbird / "parent" experiment code**, you need to migrate to an indirect approach, usually based on explicit message passing. Depending on the complexity of your task, this can either happen through notifyTools, a custom experiment API or through custom experiment code directly using cross-process APIs (likely either [message managers](https://searchfox.org/mozilla-central/source/dom/chrome-webidl/MessageManager.webidl) or [actors](https://firefox-source-docs.mozilla.org/dom/ipc/jsactors.html)).
220
+
***If you exchange raw objects between WebExtension scopes / "child" experiment code and Thunderbird / "parent" experiment code**, you need to migrate to an indirect approach, usually based on explicit message passing. Depending on the complexity of your task, this can either happen through notifyTools, a custom experiment API or through custom experiment code directly using cross-process APIs (likely either [message managers](https://github.com/mozilla-firefox/firefox/blob/main/dom/chrome-webidl/MessageManager.webidl) or [actors](https://firefox-source-docs.mozilla.org/dom/ipc/jsactors.html)).
221
221
* As a consequence, **if you load JavaScript modules in "child" experiment code**, you will now get separate instances of the JSM: each process has its own instance, and there could be multiple child processes. If you keep using JSMs from "child" code, you may furthermore need to manually unload these separate instances on API shutdown (`ExtensionAPI.onShutdown`), even if you use a catch-all unloading solution like CachingFix or the WindowListener API.
Copy file name to clipboardExpand all lines: releases/cadence.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
Thunderbird follows a release train model to ensure timely and predictable releases. This approach allows for regular feature rollouts, stability improvements, and bug fixes.
6
6
7
7
### General Release Cadence
8
-
The general release cadence consists of 4-week cycles, with each branch corresponding to a specific release channel. Each branch, starting from comm-central, is based on the previous branch.
8
+
The general release cadence consists of 4-week cycles, with each branch corresponding to a specific release channel. Each branch, starting from main, is based on the previous branch.
9
9
10
10
11
11
@@ -15,35 +15,35 @@ The general release cadence consists of 4-week cycles, with each branch correspo
15
15
16
16
#### **Thunderbird Daily**
17
17
-**Release Timeline**: A new major version of Thunderbird Daily begins every 4 weeks.
18
-
-**Releases**: Thunderbird Daily is automatically released on a daily basis from comm-central.
18
+
-**Releases**: Thunderbird Daily is automatically released on a daily basis from main.
19
19
20
20
#### **Thunderbird Beta**
21
21
-**Release Timeline**:
22
22
- A new major version of Thunderbird Beta begins every 4 weeks.
23
-
- 4 weeks after Daily starts for a new version, comm-central is merged into comm-beta.
23
+
- 4 weeks after Daily starts for a new version, main is merged into beta.
24
24
-**Releases**: Thunderbird Beta for this version is released weekly for the next 3 weeks.
25
25
-**Beta 1**: Includes the merged code.
26
26
-**Beta 2 and above**: Include any new uplifts.
27
27
28
28
#### **Thunderbird Release**
29
29
-**Release Timeline**:
30
30
- A new major version of Thunderbird Release begins every 4 weeks.
31
-
- 3 weeks after Beta starts for a new version, comm-beta is merged into comm-release.
31
+
- 3 weeks after Beta starts for a new version, beta is merged into release.
32
32
- 1 week after this merge, the monthly Thunderbird Release is published.
33
33
-**Releases**: Thunderbird Release is released every 4 weeks, with point releases as needed every 2 weeks.
34
34
35
35
#### **Thunderbird ESR (Extended Support Release)**
36
-
-**Release Timeline**: The code from comm-release is merged into comm-esr\<version\> once a year.
36
+
-**Release Timeline**: The code from comm-release is merged into esr\<version\> once a year.
37
37
-**Releases**: Thunderbird ESR is released every year, typically in July, with point releases as needed every 2 weeks.
38
38
39
39
---
40
40
41
41
### **Stabilization Milestones**
42
42
43
43
#### **Daily Soft Code Freeze**
44
-
- A 1-week soft code freeze occurs for comm-central prior to merging into comm-beta.
44
+
- A 1-week soft code freeze occurs for main prior to merging into beta.
45
45
- During this time:
46
-
- Risky code should not land in comm-central.
46
+
- Risky code should not land in main.
47
47
- Features controlled by a feature flag that were disabled in Daily should not be enabled.
48
48
49
49
#### **Pre-Merge Reviews**
@@ -63,7 +63,7 @@ The general release cadence consists of 4-week cycles, with each branch correspo
Copy file name to clipboardExpand all lines: releases/channels.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
Thunderbird provides releases through four distinct channels, each serving a unique purpose. Below are the channels, their corresponding branches, and a summary of their purpose:
4
4
5
-
-**Thunderbird Daily (comm-central)**: Where development and testing begin, and new features are developed.
6
-
-**Thunderbird Beta (comm-beta)**: The monthly stabilization release.
7
-
-**Thunderbird Release (comm-release)**: The official monthly release.
8
-
-**Thunderbird ESR (comm-esr)**: The official annual extended support release.
5
+
-**Thunderbird Daily (main branch)**: Where development and testing begin, and new features are developed.
6
+
-**Thunderbird Beta (beta branch)**: The monthly stabilization release.
7
+
-**Thunderbird Release (release branch)**: The official monthly release.
8
+
-**Thunderbird ESR (esr### branch)**: The official annual extended support release.
9
9
10
10
These four channels offer increasing levels of stability, increasing as code moves from Daily to Beta and being the highest in Release and ESR.
0 commit comments