From MozillaWiki
Jump to: navigation, search


Gecko/layout bugs need a testcase is no longer available. I can't tell whether this text should be linked - is it still useful?

 Rrbd (talk) 05:50, 30 June 2021 (UTC)

1.1a vs. 1.0b

"Testers who wish to test all the latest changes in preparation for a second release should download and use recent nightly trunk builds"

Is there any information about this "second release" that this can link to? I couldn't find a SeaMonkey1.1 or SeaMonkeySecondRelease wiki page. I assume it's based off a trunk Gecko engine beyond 1.8, is there information about that? Does it have the XRE and chrome merges mentioned in some pages?

For what it's worth, after a bit of puzzling between different "latest" directories, I installed the seamonkey-1.0b.en-US.win32.installer.exe of 03-Nov-2005 and so far it seems every bit as good as SeaMonkey 1.0alpha.

Skierpage 18:55, 3 Nov 2005 (PST)

(removed to reduce confusion, was to late last night.) ... There are no real informations about Second Release (a.k.a. SM 1.1 or 1.5). At first we need to fiddle a real First Release. -- Alexander Opitz (opi) 12:09, 4 Nov 2005 (PST)
No, the term "first release" has always meant SeaMonkey 1.0. The term "first release" was originally used because at the time the name and version number of the first release was unknown. The term "second release" refers to the next major release of SeaMonkey, which will be created off the current trunk. Sorry it's so confusing; maybe someone can clean up the terminology so it's not as confusing. -- Schapel 05:04, 5 Nov 2005 (PST)

Builds & Branchs

Nightly builds refers to builds (versions) made every night. So last midnight nightly-build has the latest changes and bugfixes (this is the usual, but actually there are builds at any time in the morning, afternoon or night).

Branch refers to developing based on a spcific version, so "Gecko 1.8 branch" refers to Gecko 1.8, Gecko 1.8.1, etc.

Nightly XXXXXX #.# branch builds refers to nightly builds based on an specific version. For example, you can have a last nightly Mozilla Suite 1.7 branch build with a nightly Gecko 1.7 branch build, wich have latest bugfixes to both Mozilla Suite 1.7 and Gecko 1.7, but no new features like CSS3-columns; and a last nightly SeaMonkey 1.0 branch build with last midnight Gecko 1.8 branch build, wich have latest bugfixes to SeaMonkey 1.0 and Gecko 1.8, but no new features like... ehmmm... scrollable table bodies?

Trunk builds are, by definition (AFAIK), nightly builds. They have all features being developed, even if the feature has not a target release defined. Let use scrollable table bodies (STB) as example. Suppose i submit a patch for this feature, it enters in latest trunk, but not in latest nightly Gecko 1.8b build because STB is not a feature planned for the final release Gecko 1.8. Maybe, in the future, Gecko drivers add it to Gecko 1.8.1 branch, or skip to Gecko 1.9 branch, or it may stay in trunk until it will be added in Gecko 2.0 branch.

I hope I clarify and not mess it more.

PD: Is there any beter way to separate a big comment like this?

--Sergiodf 08:30, 5 Nov 2005 (PST)


What's stopping Talkback from being enabled in branch builds and releases? Is there a way I can manually add it to a 1.0.1 install? ACupOfCoffee 11:21, 1 May 2006 (PDT)

In short, no you cannot manually add it. Though I cannot recall enough to articulate the Reason Asa gave me over a year ago when I wanted to enable it for my own builds. Sorry. --Justin Wood (Callek) 12:31, 1 May 2006 (PDT)