|
|
Line 1: |
Line 1: |
| {{SeaMonkey-Resources}} | | {{SeaMonkey-Resources}} |
| Bugzilla-FAQ you can find [[SeaMonkey/Bugzilla-FAQ|here]]
| | {{Template:OutdatedSM}} |
|
| |
|
| __TOC__ | | __TOC__ |
Line 6: |
Line 6: |
| == What is the new SeaMonkey official name? == | | == What is the new SeaMonkey official name? == |
| : The new name is SeaMonkey. Please consult the [[SeaMonkey:Name_And_Version|Branding Page]] for more information on this. | | : The new name is SeaMonkey. Please consult the [[SeaMonkey:Name_And_Version|Branding Page]] for more information on this. |
|
| |
| == What version numbers will be used for the new releases? ==
| |
| : The first version was 1.0 to distinguish the difference between the officially supported Mozilla Application Suite 1.7.x and the new community-supported SeaMonkey suite. This has been done for the benefit of our business users who will need to make an informed decision about upgrade paths.
| |
|
| |
| : The second version was 1.1 and a feature update to 1.0. The third version was 2.0 and a whole new release based on the Mozilla 1.9.1 platform. The forth version was 2.1, based on Mozilla 4.0.1. Starting with version 2.2, SeaMonkey joined the rapid release train, which means new releases every six weeks and the end of minor updates (emergency security fix releases may still happen, though).
| |
|
| |
| : With the adoption of the rapid release cycle, release candidates (RCs) have been replaced by beta versions. As such, beta versions now identify themselves as release versions, i.e. they cannot be distinguished from release versions and the final beta is equal to the final release. Consequently, users on the beta channel are not upgraded to the final release because they already have it when they upgrade to the final beta. Instead, they are upgraded to the first beta of the next release once released.
| |
|
| |
|
| == Where do I download SeaMonkey? == | | == Where do I download SeaMonkey? == |