450433 - Release Notes for Camino 2.0a1

Status: RESOLVED FIXED

(Camino Graveyard :: General, defect)

Description

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

Comment 1

[Oscar van Vliet]

Adding a draft release notes to the 2.0 alpha 1 pre release nightlies would be good..

Comment 2

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

Attachment: Draft notes

Here are the draft notes.  Since the first sentence of the alphabeta notes got axed by the time we got to the final 1.6 notes (it used to move to the middle of the first pgh in the final notes), I've reworked it a bit here.

Sam, Stuart, let me know if you have any (other) thoughts on the notes.

Comment 3

[Samuel Sidler (old account; do not CC)]

venerable?

I think you should move the recently closed pages line to be under Bookmarks and rename the section "Bookmarks & History".

"frontmost" -> "front-most" ? I'm not sure...

Merge the two control characters lines.

I'm not a fan of "mousing". Hovering?

"Camino now requires Shockwave Player 11 or newer." It does? You mean I need to have Shockwave installed to use Camino? ;) I can't think of a better way to write it though...

Comment 4

[Stuart Morgan]

(In reply to comment #3)
> venerable?

Agreed. Venerable to me says "All you people who said Camino was no longer relevant? We agree!"

> I can't think of a better way to write it though...

"Camino no longer supports Shockwave 10 and earlier. Shockwave 11 or later is supported" ?

Random and incomplete list of other comments (I'll take another look later):
- We list lots of minor stuff in Camino's UI, but almost nothing about the Gecko 1.9 changes, which is the huge driver for this release. I'm thinking we could have a whole section about the new Gecko and include some of the more noticeable fixes (which has the added advantage of allowing us to break up the kind of run-on-y sentence there now). Some thoughts for things in addition to what we already have (which need wording love)
  - Improved standards support (we don't have to use the A-word, but it's worth calling out as a topic)
  - Scroll bars in hidden portions of web pages no longer display
  - Vastly improved Flash performance
  - Better handling of pages with large tables
  - ???

- Change the last sentence of the 1Password part to something along the lines of "Make sure that you are running the latest version of 1Password, and if you continue to experience issues, <disable and contact, blah blah>". That comes across as less confrontational, and we know that at least some of the last crop of issues have been fixed in the latest versions (beta or otherwise, I'm not sure).

- No one cares about the implementation of the HTML importer, so let's just say that it's more stable, and has better support for bookmark attributes and exported Firefox 3 bookmarks

- "keyboard loop" feels jargon-y, and we have a few scattered comments about tabbing. How about a single comment along the lines of "Full Keyboard Access now moves correctly through all parts of the browser window"?

- All the bits about control characters seem like they could be a single "Invalid characters are now handled better in the location bar, search field, and bookmarks" sort of thing.


Do we also want to trim some of the tiny polish stuff, and lump them under one or two catch-alls? Maybe expanding Gecko 1.9 will help, but right now reading the list it feels like lots of small things that don't add up to a 2.0. I feel like we need to emphasize big things more, and small things less.

Comment 5

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

Attachment: Notes, v2

This makes most of the changes suggested in the comments and others in the spirit of those comments.  A number of the smaller changes have been collapsed into a single note, other notes have been reworded, and the Gecko section is now substantial and seems to tower above the rest of the page (though if you've thought of other 'important-to-us' Gecko changes, I'm happy to add them, too). I've also re-ordered each section to put the more significant changes first and moved a couple of notes between sections.

I left 'frontmost' alone; 'front' by itself sounded problematic to me, since by definition this change enables things when the browser window is not the front window.  Not married to it if you feel strongly the other way.

I left two stand-alone keyboard accessible items, the tab bar and the pop-up blocker, because they've been pretty long-standing sore thumbs from the otherwise sometimes-passable loop, and I felt that it was important to call them out specifically.  The rest of the keyboard accessibility notes have been collapsed into one main note.

We're also "popular" now ;)

Sam, Stuart, do these feel better?

Comment 6

[Stuart Morgan]

Comment on attachment 341884 [details]
Notes, v2

Ship it!

Comment 7

[Samuel Sidler (old account; do not CC)]

Looks good to me!

Comment 8

[Samuel Sidler (old account; do not CC)]

Comment on attachment 341884 [details]
Notes, v2

r=me

Comment 9

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

Checked in on cvs trunk, with r=ss and sr=smorgan as discussed at the meeting.  We'll let mento take a crack at fixing anything we missed during the next milestone release.