Camino 1.5 Release Candidate 2 [do not announce]

[Uncle Asad]

We're happy to present the first release candidate for Camino 1.5 (yes, 1.5).

There may be another build pending MoCo's certification of the version of Gecko we're using as "final"; there may also be lingering security bugs (again pending MoCo certification of the Gecko inside), and so forth.

To make sure this release is just as solid as 1.0, we'd appreciate everyone running it until we make the final 1.5 release (or a second release candidate supersedes it). Like right before 1.0, if you've been using trunk nightlies, please use this instead; you guys and ladies are a large chunk of our nightly testers, and we need your help to ensure everything is just right. (If you're using branch nightlies, there will be nothing new landing, so please test this RC build instead of the nightlies, too.)

If you notice any regressions from 1.0.4 or 1.1b, please let us know ASAP; similarly, if you find any serious bugs. Talkback is good, but real live reports here or in Bugzilla are even better.

Thanks for your help!

PLEASE do not post this build to MacUpdate, VersionTracker, iusethis, Digg, TUAW, Slashdot, etc.

Edit: RC2 -
Camino 1.5 Release Candidate 2

[macwish]

Version 1.5rc1 quits unexpectedly every time I try to launch it. Startup would begin, spinning beach ball would appear briefly and then 1.5 quit. Bug report submitted. No problems like this ever before with any version of Camino. Crash report sent to Bugzilla.

G4 iMac 1Ghz, OS X 10.4.9.

[macwish]

Problem solved (in part). Turns out that Camino 1.5 is incompatible with 1Password. Uninstalling 1Password allows Camino 1.5 to launch and function properly. Problem reported to 1Password developer. Since I find 1Password essential to browsing, I will stick to Camino 1.0.4 until incompatibility is resolved.

[alreadymental]

Just downloaded Camino 1.5 so far great:)

[alreadymental]

Wasn`t great for long as i just received the "Beachball" of death, and had to do force quit:(

[macwish]

Solution to incompatibility of Camino 1.5RC and 1Password. At suggestion of 1Password developer, downloaded beta versioqn of 1Password (version 2.4 Beta4). The beta version and Camino 1.5 work together without any problems.

[froodiantherapy]

Wasn`t great for long as i just received the "Beachball" of death, and had to do force quit:(

Unfortunately, this information on its own isn't very useful. Next time this happens, try taking a sample of the application (using Activity Monitor), and we'll see if it's a problem which can be addressed.

[wtmcgee]

I wondered why beta.caminobrowser.org was down ... I'd assume these two events are related?

So far, so great, by the way.

[widge34]

Well the sites i would avoid because Camino could not handle the Flash now seem to be fine using 1.5. Only downloaded 1.5 10 minutes ago so its early days. So far so good.

[Old Macskeeball]

It's a minor thing, but I noticed that the EULA that appeared when I mounted the DMG still said "Version: 1.1."

[smorgan]

That's the license version; the Camino 1.0.x EULA said the same thing.

[seldon]

After manually removing CaminoSession (the uninstaller seemed to do exactly the same thing as the installer.... very helpful), 1.5 beta/alpha/whatever is up and running. It seems a bit faster then 1.0.4. In fact, it seems quite a bit snappier when opening new tabs/windows.

I'll report back after some heavier usage.

[xanderatallah]

I don't understand why the txt file that came with 1.5 said one of the new features was "accepting cookies for the session only" yet the privacy preference pane is unchanged.

And how long will it be until 1.5? There are no differences at all from 1.1b that I notice... What's the difference?

[Lost User 220168]

Camino was feature frozen at 1.1b, so there are no new features in the RC, just many bug fixes.

[smorgan]

I don't understand why the txt file that came with 1.5 said one of the new features was "accepting cookies for the session only" yet the privacy preference pane is unchanged.

Individual cookies can now be accepted as session cookies, and all cookies from given sites can be accepted automatically as session cookies, both of which are new features since 1.0.x. Accepting *all* cookies as session cookies is still a hidden preference only.