SEAMONKEY_2_35_BUILD1

[Philip Chee]

Added tag SEAMONKEY_2_35_BUILD1 for changeset e6dcddf50595. CLOSED TREE a=release
http://hg.mozilla.org/releases/comm-release/rev/4fc18a1917bc

Added tag SEAMONKEY_2_35_RELEASE for changeset e6dcddf50595. CLOSED TREE a=release SEAMONKEY_2_35_RELEASE_BRANCH
http://hg.mozilla.org/releases/comm-release/rev/ab1df175fbc9

Phil

[RDaneel]

Cool - so is this essentially the same set of sources used to create your "2.35y" build?

And for that matter, where would I go to see this "BUILD1"? The FTP site that I have always gone to has been re-organized recently, and [ominously] SM things moved to an "archives" area.

And thanks for your part, Phil, in keeping SM "alive" - to the extent it is.

[Philip Chee]

Cool - so is this essentially the same set of sources used to create your "2.35y" build?

Yes

And for that matter, where would I go to see this "BUILD1"? The FTP site that I have always gone to has been re-organized recently, and [ominously] SM things moved to an "archives" area.

Ewong still has a few hiccups to overcome but rest assured that they are on the way!

And thanks for your part, Phil, in keeping SM "alive" - to the extent it is.

You're welcome

Phil

[4td8s]

check here for the candidate builds of SM 2.35, RDaneel.

[RDaneel]

Thanks... unfortunately, none of the "BUILDn" trees has any Windows builds, which is what I am after.

[colfer]

It has arrived.
/pub/seamonkey/nightly/2.35-candidates/build3/unsigned/win32/en-US

[TPR75]

It has arrived.
/pub/seamonkey/nightly/2.35-candidates/build3/unsigned/win32/en-US

Not yet:
http://ftp.mozilla.org/pub/seamonkey/releases/2.35/

"Patience, young Padawan" :>

[WaltS48]

If you already have SeaMonkey 2.33.1 installed it should update, and I believe it will show up here when released.

The SeaMonkey® Project

[4td8s]

If you already have SeaMonkey 2.33.1 installed it should update, and I believe it will show up here when released.

The SeaMonkey® Project

SM 2.35 will eventually show up there but not on August 31 (most likely early September).

ewong sure has had many challenges he has faced in making the SM 2.35 release as mentioned in these SM blogs:
https://blog.seamonkey-project.org/2015 ... -bad-news/
https://blog.seamonkey-project.org/2015 ... ck-status/

[LuvKomputrs]

Am using 2.35-candidates/build3/unsigned/win32/en-US/ and having no issues at all.
KUDOS to ewong and everyone else at the SeaMonkey project for keeping my favorite browser going!

[vladmir]

http://ftp.mozilla.org/pub/seamonkey/releases/2.35/
http://download.cdn.mozilla.net/pub/mozilla.org/seamonkey/releases/2.35/

[Pim]

I see that the official release is 2.35 rather than the 2.37 I would have expected by now. (The official Mozilla Firefox is v40, so some simple math would have SM at v2.37, like the Tinderbox Release builds.)

So the question is, since the official release is FIVE versions behind the very latest Gecko engine, the question is, how are we calling the versions inbetween now?
2.40 is the "trunk", 2.39 the "aurora", 2.38 the "beta". What about 2.36 and 2.37? Is 2.36 already a "candidate"?

[-Px-]

So the question is, since the official release is FIVE versions behind the very latest Gecko engine, the question is, how are we calling the versions inbetween now?
2.40 is the "trunk", 2.39 the "aurora", 2.38 the "beta". What about 2.36 and 2.37? Is 2.36 already a "candidate"?

2.36 and 2.37 are "skipped"

[Pim]

Oh... That was quick.