Closed Bug 324439 Opened 18 years ago Closed 18 years ago

Land ChatZilla 0.9.70 on branch

Categories

(SeaMonkey :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Gijs, Assigned: Gijs)

Details

(Keywords: fixed-seamonkey1.1a, fixed1.8.1, relnote)

Attachments

(2 files)

The ChatZilla developers would like to land the latest version (current cvs trunk alias 0.9.70) on branch. There has been a good amount of work done since Gecko 1.8 branched in August, and we'd hate to have the Seamonkey 1.0 builds miss it. Please consider incorporating the trunk changes, even though we're rather late requesting you to do so.
Attachment #209381 - Flags: approval-seamonkey1.1?
Attachment #209381 - Flags: approval-seamonkey1.0?
Comment on attachment 209381 [details] [diff] [review]
Patch from branch to trunk

a=me for SM1.1
Despite the size of the patch there does not seem to be too many locale changes but it is probably best kairo comments on that.
Attachment #209381 - Flags: approval-seamonkey1.1? → approval-seamonkey1.1+
I'd been sloppy, the previous patch modified CVS files, and didn't include a new file. To make sure this goes alright when anything gets checked in, here is a patch without CVS files and with text-serializer.js included. Apologies for bugspam.
Attachment #209404 - Flags: approval-seamonkey1.0?
Attachment #209404 - Flags: approval-seamonkey1.1+
Attachment #209381 - Flags: approval-seamonkey1.0?
Even more bugspam, carrying across a=me for SM1.1 and removing old ?SM1.0 request
Comment on attachment 209404 [details] [diff] [review]
Patch that doesn't modify CVS files and has text-serializer.js

After discussions with Kairo, it is too late for 1.0 and the L10n people, so minusing for SM1.0/MOZILLA_1_8_0_BRANCH but it can go into SM1.1/MOZILLA_1_8_BRANCH
Attachment #209404 - Flags: approval-seamonkey1.0? → approval-seamonkey1.0-
Alright, I understand, I guess. If, however, the main issue is l10n, would it be possible to include a note in the release notes that it is possible to download a newer version of ChatZilla from addons.mozilla.org? This would be in English, of course, but I think that some people wouldn't mind that as much.
Keywords: relnote
(In reply to comment #6)
> Alright, I understand, I guess. If, however, the main issue is l10n, would it
> be possible to include a note in the release notes that it is possible to
> download a newer version of ChatZilla from addons.mozilla.org? This would be in
> English, of course, but I think that some people wouldn't mind that as much.
> 

Yes.  As I understand it, we should recommend *against* installing the Chatzilla that is included with SeaMonkey and use the one from a.m.o instead.  Is that correct?
Status: NEW → ASSIGNED
There is not much sense in discouraging people from installing ChatZilla from the install package. The then-installed version will simply be completely overwritten by the new version, without any problems. Write access to the application dir is necessary for this, but that'd also be required if ChatZilla wasn't installed yet.

To suggest text that could be on the release notes:

"SeaMonkey 1.0 doesn't contain the latest version of ChatZilla. The most recent release can be installed <a href="https://addons.mozilla.org/extensions/moreinfo.php?id=16">here</a>."

Assignee: general → gijskruitbosch+bugs
Status: ASSIGNED → NEW
(In reply to comment #8)
> There is not much sense in discouraging people from installing ChatZilla from
> the install package. The then-installed version will simply be completely
> overwritten by the new version, without any problems. Write access to the
> application dir is necessary for this, but that'd also be required if ChatZilla
> wasn't installed yet.
> 
> To suggest text that could be on the release notes:
> 
> "SeaMonkey 1.0 doesn't contain the latest version of ChatZilla. The most recent
> release can be installed <a
> href="https://addons.mozilla.org/extensions/moreinfo.php?id=16">here</a>."
> 

Done
Checked in on the 1.8 branch.

Changing to FIXED since this needs no trunk checkin, won't get 1.8.0 checkin, and CTho has added the release note. QA, please verify :-).
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Whiteboard: fixed-seamonkey1.1
Whiteboard: fixed-seamonkey1.1
You need to log in before you can comment on or make changes to this bug.