668427 - Create (en-US) Major Update billboard page for SeaMonkey 2.0->2.2 update

Status: RESOLVED FIXED

(SeaMonkey :: Release Engineering, defect)

Description

[Justin Wood (:Callek)]

Jens,

Can you throw together a MU Billboard page for our Major Update so we can test this now that I have automation ready to try!

We'll want to allow l10n the chance to localize this by the time we go to offer the update, so we should build in some means for %locale% expansion (we'll check in en-US versions for each locale pending an update by the locale).

Please come up with some dir/file nameing structure at your discretion, under https://www.mozilla.org/start/*

The update-billboard-size is *fixed* inside the app itself, and I have a very very rough MU offer sitting on SeaMonkey 2.0 atm (pointing at https://www.mozilla.org/start/index.html for now) you have to manually update your update channel to "betatest" in order to see it, incase you want to test the size/display side of it.

For reference:

Fx *->4.0:
https://www.mozilla.com/en-US/firefox/4.0/details/
Fx 4.0->5.0 (not currently offered, and page is 404)
https://www.mozilla.com/en-US/firefox/5.0/details/
Fx *->3.6 (old update offer)
http://www.mozilla.com/en-US/firefox/3.6/details/index.html

Tbird 3.1->5.0:
https://www.mozilla.org/en-US/thunderbird/5.0/details/index.html
Tbird 3.3a3->Tb50.b1 (both miramar, so must have been a test)
http://www.mozillamessaging.com/en-US/thunderbird/5.0/details/index.html

Comment 1

[Jens Hatlak (:InvisibleSmiley)]

Attachment: billboard ZIP

Thanks for the links, that's what I needed. I've seen the dialog when I checked with an older Firefox build but didn't extract the URLs then.

Proposed directory scheme (cf. the ZIP):
<version>/<locale>/index.html
style/(... CSS/images)

I primarily looked at the FF 3.6 and TB 5 billboard pages (which are very similar on the HTML/CSS level) and fused their essence into a page for SM. This is what I did:
- copied and reformatted the XHTML structure
- copied the bullet and box top/bottom images
- copied the header bg and logo (64x64) images from the SeaMonkey Artwork page
- fused content.css and update-3.css into billboard.css
- applied SM color scheme and used a sans-serif font for the h1 (looks great with Segoe UI, maybe not that much with Arial, don't know about Helvetica)
- adapted strings, esp. the three key points

I haven't checked how it looks in-app but since the result looks very similar to the originals regarding sizes I don't foresee a problem there.

Regarding the strings, we can see a pattern if we compare the FF, TB and SM versions. There's "free" in all three, though in different places, and of course the call for upgrading. More importantly, each app has different key points:
- FF: telling the users that the add-ons will keep working and it's better/faster/safer and more secure
- TB: improvements and speed
- SM: I think telling that all add-ons will keep working would be a lie, so I scratched that. Listing individual improvements is useless given the little space we have, but we should definitely mention it in general. Finally, speed should be much better compared to 2.0.

I hope you like it! We can surely talk about the upgrade link destination or individual strings, but I cannot provide any new graphics within the short time I've left before going on vacation.

Comment 2

[Robert Kaiser]

Checked in as r92304.
Mark fixed if this works as expected.

Comment 3

[Robert Kaiser]

BTW, as Callek mentioned in bug 670320, it might be even nicer if that was formatted as HTML5. ;-)

Comment 4

[Jens Hatlak (:InvisibleSmiley)]

(In reply to comment #3)
> BTW, as Callek mentioned in bug 670320, it might be even nicer if that was
> formatted as HTML5. ;-)

Just reading your comment via bugmail I didn't get what you mean, since there is no formatting involved. But looking at bug 670320 I see that you really meant dropping the XML validity requirement and changing the doctype. We can surely do that, and I agree it's easier to maintain, but certainly not nicer than valid XHTML. ;-)

That said, Callek, feel free to mark fixed whenever you like. I don't have mozilla.org access anyway and have lost track a bit to which degree this has been fixed. I saw the billboard page after updating twice from 2.0b2, though, so I guess this is done.

Comment 5

[Robert Kaiser]

(In reply to comment #4)
> We can surely do that, and I agree it's easier to maintain, but certainly
> not nicer than valid XHTML. ;-)

Well, except that HTML5 is where the future lies, and XHTML is more or less deprecated and dying out. ;-)

Comment 6

[Jens Hatlak (:InvisibleSmiley)]

(In reply to comment #5)
> Well, except that HTML5 is where the future lies, and XHTML is more or less
> deprecated and dying out. ;-)

Which may be relevant for the web, but hardly for an internal page. XML does have its right to exist, and I think this case is in between.