Closed
Bug 426286
Opened 16 years ago
Closed 16 years ago
Update description for 1.6final
Categories
(Camino Graveyard :: Product Site, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: alqahira, Assigned: alqahira)
Details
Attachments
(2 files)
For 1.6final, we need to decide on the text we're going to use for the update description, and we need to do it very soon so we can get the en-US text to localizers. For the betas we've been using part of the text from the relnotes (the paragraph with the "beta" warning) plus an optional "we fixed some bad crashes" notice and off-loaded the "what's changed" to preview.cbo and thence the wiki for more detail. Do we want to 1) Use the 1.6 release notes in their entirety 2) Use the introductory paragraphs of the 1.6 release notes 3) "Write" something "new" (perhaps an arrangement of parts of the former) For reference, draft of the relnotes are at http://wiki.caminobrowser.org/Releases:1.6:Notes
Assignee | ||
Comment 1•16 years ago
|
||
This is what we'll be using for 1.6 final.
Assignee | ||
Comment 2•16 years ago
|
||
Marcello, this bug is a good place to attach any translations of the update description that you get. Since users upgrading from 1.5.5 won't be using software update, we won't block on this, but if any of the l10n communities have a localized 1.6b4 out for testing, those users will get software update, and having a localized description would be nice for them.
Summary: Decide on update description format for 1.6final → Update description for 1.6final
Comment 3•16 years ago
|
||
Updated•16 years ago
|
Assignee: samuel.sidler → alqahira
Assignee | ||
Comment 4•16 years ago
|
||
FIXED on stage for 1.6 (and on live with update-check-test). Stuart did a little testing earlier using update-check-test and got Italian text :)
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•16 years ago
|
||
Marcello, because of some load issues we had to redirect everyone to a single static update file (which has the English text). Sorry about that :-(
You need to log in
before you can comment on or make changes to this bug.
Description
•