If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

README.txt should be updated

RESOLVED FIXED

Status

()

Core
General
--
trivial
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Hendrik Maryns, Assigned: Peter Weilbacher)

Tracking

Trunk
x86
OS/2
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
The readme file contains the following line:

unzip thunderbird-1.0-os2.zip -d c:\thunderbird-1.0

the 1.0 should become something like 2.0, or perhaps even better, XX, with a remark that XX represents the current version number.

Comment 1

11 years ago
Well, it says "i.e." that so...

The source is here, if you want to make a patch
http://lxr.mozilla.org/seamonkey/source/mail/locales/en-US/os2/README.txt
(Reporter)

Comment 2

11 years ago
i.e. means: ‘with other words’, not ‘for example’, that is e.g.  So if you want to stick to abbreviations, i.e. should become e.g.  I’d prefer a similar remark as in point 1 of the list, though.  I’ll make a patch as soon as I am on my other puter once again...
(Assignee)

Comment 3

11 years ago
OK, the version number is not a big deal, it should be clear from the above that it is an example, even though it says "i.e." not "e.g.". But that's easily changed. I'll take the chance to change the typical filenames given in that file to what is used now.
Component: Installer → General
Product: Thunderbird → Core
Hardware: Macintosh → PC
(Assignee)

Comment 4

11 years ago
Created attachment 243923 [details] [diff] [review]
update readmes of all three products

Anything else I should change while I am there?
Assignee: mscott → mozilla
Status: NEW → ASSIGNED
(Reporter)

Comment 5

11 years ago
I don’t get it, I think it is a good patch, but why do you still keep references to FF 1.0.1?  Why not do the x.x.x. trick in the unzip example too?
(Assignee)

Comment 6

11 years ago
I don't plan to update the number for every release and if it says x.x.x then the next user will come as ask "There is no x.x.x in the package but 2.0.0.2 instead what should it do?" (Things like that actually do happen!)
With 1.0.1 and "e.g." it should now be clear at least that it is an example...
(Assignee)

Updated

11 years ago
Attachment #243923 - Flags: review?(mozilla)

Comment 7

11 years ago
Comment on attachment 243923 [details] [diff] [review]
update readmes of all three products

r=mkaply
Attachment #243923 - Flags: review?(mozilla) → review+
(Assignee)

Comment 8

11 years ago
Checked into trunk.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.