521614 - Release Notes for Camino 2.0

Status: RESOLVED FIXED

(Camino Graveyard :: General, defect)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Need to have these ready before we can RC.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: 2.0 relnotes, take 1

Here's the first stab at the Release Notes text for 2.0.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Er, I missed that F4M 2.3.0.14 (taking a page from the Flash playbook) came out today, so we want to use that number instead of the 2.2.finally.fixed-our-stupid-bug number (which is easier to confuse with 2.2.broken.screws-up-your-pages).

Comment 3

[Eiichi]

Just for reference;
Flip4Mac version 2.2.3.7 works better than 2.3.0.14 on 10.4 (Intel) .

Comment 4

[Stuart Morgan]

Comment on attachment 406633 [details]
2.0 relnotes, take 1

Looks great! Thanks for wading through bugzilla to make the list :)

s/still running Mac OS X 10.3.9/running Mac OS X 10.3.9/
s/potentially malicious/many potentially malicious/
"entire content" feels a bit wrong; maybe "entire contents" or "full contents"?
s/context menu item/contextual menu item/
s/Camino 2.0 includes a new/Camino now includes an/ (for parallel structure with the other bullets)

Move "Web content support" to the top, since that's really important

s/This behavior is fixed/This is fixed/
Any objection to removing the 1Password section, since we have the in-app warning for those affected? If we do remove it, we should change "software" to "plugins" in the heading.

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #4)

> "entire content" feels a bit wrong; maybe "entire contents" or "full contents"?

I went with "entire contents" to keep from directly repeating the words in its header.

> Any objection to removing the 1Password section, since we have the in-app
> warning for those affected? If we do remove it, we should change "software" to
> "plugins" in the heading.

Done, with "plug-ins" per style.

> Move "Web content support" to the top, since that's really important

We've always listed this last (since 1.0).  Sam didn't want it included at all.  I'd rather lead with features that end-users understand and can relate to, rather than things they don't really understand.

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Stuart, see comment 5.

Comment 7

[Stuart Morgan]

(In reply to comment #5)
> We've always listed this last (since 1.0).  Sam didn't want it included at all.
>  I'd rather lead with features that end-users understand and can relate to,
> rather than things they don't really understand.

Fair enough. I was just thinking about the fact that almost all the problems we hear about Camino users having recently are addressed by this item. I guess people who understand it will already know for the most part though.

Comment 8

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Release Notes for Camino 2.0, as checked in

Final version.

Comment 9

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #8)
> Created an attachment (id=406963) [details]
> Release Notes for Camino 2.0, as checked in
> 
> Final version.

Which is to say, with the changes outlined in comment 5 and web content at the end, where it belongs.

Landed on cvs trunk and CAMINO_2_0_BRANCH along with installer Makefile changes to use it.