SEAMONKEY_2_35_BUILD1
- Philip Chee
- Posts: 6475
- Joined: March 1st, 2005, 3:03 pm
- Contact:
SEAMONKEY_2_35_BUILD1
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
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
-
- Posts: 604
- Joined: January 19th, 2004, 2:43 pm
- Location: Puget Sound, WA
- Contact:
Re: SEAMONKEY_2_35_BUILD1
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.
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
- Posts: 6475
- Joined: March 1st, 2005, 3:03 pm
- Contact:
Re: SEAMONKEY_2_35_BUILD1
RDaneel wrote:Cool - so is this essentially the same set of sources used to create your "2.35y" build?
Yes
RDaneel wrote: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!
RDaneel wrote:And thanks for your part, Phil, in keeping SM "alive" - to the extent it is.
You're welcome
Phil
-
- Posts: 784
- Joined: June 24th, 2009, 1:07 pm
Re: SEAMONKEY_2_35_BUILD1
check here for the candidate builds of SM 2.35, RDaneel.
-
- Posts: 604
- Joined: January 19th, 2004, 2:43 pm
- Location: Puget Sound, WA
- Contact:
Re: SEAMONKEY_2_35_BUILD1
Thanks... unfortunately, none of the "BUILDn" trees has any Windows builds, which is what I am after.
- colfer
- Posts: 643
- Joined: December 4th, 2002, 9:34 am
- Location: Bear
Re: SEAMONKEY_2_35_BUILD1
It has arrived.
/pub/seamonkey/nightly/2.35-candidates/build3/unsigned/win32/en-US
/pub/seamonkey/nightly/2.35-candidates/build3/unsigned/win32/en-US
-
- Posts: 1353
- Joined: July 25th, 2011, 8:11 am
- Location: Poland
Re: SEAMONKEY_2_35_BUILD1
colfer wrote: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
- Posts: 5141
- Joined: May 7th, 2010, 9:38 am
- Location: Pennsylvania, USA
Re: SEAMONKEY_2_35_BUILD1
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
The SeaMonkey® Project
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
-
- Posts: 784
- Joined: June 24th, 2009, 1:07 pm
Re: SEAMONKEY_2_35_BUILD1
WLS wrote: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
- Posts: 659
- Joined: June 9th, 2010, 8:15 am
Re: SEAMONKEY_2_35_BUILD1
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!
KUDOS to ewong and everyone else at the SeaMonkey project for keeping my favorite browser going!
-
- Posts: 319
- Joined: October 18th, 2004, 9:47 am
- Pim
- Posts: 2215
- Joined: May 17th, 2004, 2:04 pm
- Location: Netherlands
Re: SEAMONKEY_2_35_BUILD1
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"?
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"?
Groetjes, Pim
- -Px-
- Posts: 480
- Joined: April 20th, 2011, 1:56 am
Re: SEAMONKEY_2_35_BUILD1
Pim wrote: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
- Posts: 2215
- Joined: May 17th, 2004, 2:04 pm
- Location: Netherlands