Forum: Weblog comments

From that new build machines bug, I gather that the linux-x86_64 nightlies that I use, as well as any other L64 builds, are all built on one machine and are considered "experimental". Of course getting new machines is nice (I remember when SeaMonkey was being built on your own machines and then-experimental suiterunner builds for two of the three platforms couldn't even be pushed to where anyone could download them) and of course we can't expect all the luxury afforded Firefox; but I've been running Sm trunk x86_64 nightlies "live" for my day-to-day browsing, mail/news and chat since slightly over a month (let's say since openSUSE 11.3 was released on March 10) with no more trouble than the L32 builds I used before. However, I may be biased, since I am running this on a machine with a faster CPU, and a twin-core one, which means fewer deadlocks, races, etc.

Good to see things moving again. :-)

Tony, we don't want to ship anything as non-"experimental" that has no automated tests run, and with one machine, we don't have enough power to run them. The good side is that the new machines should be enough to get those tests up for 64bit Linux, so they should become "official" soon after we have those machines available.

Where can I find info about this strange folder?

http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.1b3-real/mac64/

Vladimir:
Callek is doing all the release work now, but this "strange" folder is actually the official release. The "mac" and "mac64" folders should probably be identical, I have no idea why the "mac64" one was actually copied to "mac" instead of renamed to that, but I think only Callek can explain the details there.

vlad: that strange folder was actually a mistake on my end, the only reason it exists in the mirrors is that it was created/pushed to mirrors before I removed it, and did my mac64->mac move after that, which of course, gives that old folder.

I'll get a bug on file to add it to the exclusion list.

Any schedule for comm-2.0 to branch off comm-central yet, now that Thunderbird has decided to base their Miramar releases on Gecko 5.0 (which used to be 2.2 until yesterday) and SeaMonkey 2.1 (possibly with calendar) de-facto "owns" that branch? [I don't dare to think (or to ask) what the consequences of the new mozilla-central release system and its aggressive schedule will be for the comm-central based applications, but sure hope to hear soon about it...]

OK. Well, good news then: good news from MoFo, that new machines are coming, and good news from me (I know, just one tester) that the x86_64 builds seem to be "about as good" as the i386 ones.

Thanks Robert and Justin.-)

And links (langpacks, contributed) in
http://www.seamonkey-project.org/releases/2.1b3
are to deleted folder
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.1b3/