Closed
Bug 242653
Opened 20 years ago
Closed 20 years ago
README.TXT in latest nightly mentions mozilla, not firefox
Categories
(Firefox :: Installer, defect, P3)
Tracking
()
VERIFIED
FIXED
Firefox1.0beta
People
(Reporter: peter+bmo, Assigned: bugs)
Details
(Keywords: fixed-aviary1.0)
Attachments
(1 file, 1 obsolete file)
1.26 KB,
patch
|
Details | Diff | Splinter Review |
The README.txt found in the latest nightly (2004/05/04) build is only for mozilla, not for firefox. Maybe we have to create a firefox readme file...
Updated•20 years ago
|
Flags: blocking1.0?
Flags: blocking0.9?
Comment 1•20 years ago
|
||
Removing blocking0.9 request. We've shipped with this readme since the beginning. One more release won't hurt.
Flags: blocking0.9?
Assignee | ||
Comment 2•20 years ago
|
||
Someone should make a text version of the release notes. Assigning to nobody.
Assignee: bugs → nobody
Flags: blocking1.0? → blocking1.0+
Assignee | ||
Updated•20 years ago
|
Priority: -- → P3
Target Milestone: --- → Firefox1.0beta
Comment 3•20 years ago
|
||
Please assign to me.
Assignee | ||
Updated•20 years ago
|
Flags: blocking-aviary1.0RC1+
Comment 5•20 years ago
|
||
The attached file should be considered a first draft. It is based largely on the Release Notes dated July 8.
Updated•20 years ago
|
OS: Windows XP → All
Assignee | ||
Comment 6•20 years ago
|
||
How about we just have a README that contains a link to the release notes for this version, i.e. http://www.mozilla.org/products/firefox/releases/ This removes the burden on having to keep this in sync, and makes it less of a l10n hurdle.
Comment 7•20 years ago
|
||
(In reply to comment #6) > How about we just have a README that contains a link to the release notes for > this version, i.e. That's an interesting idea. It would certainly be the easiest answer. I will mark this bug FIXED based on that solution.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 8•20 years ago
|
||
(In reply to comment #7) > (In reply to comment #6) > > How about we just have a README that contains a link to the release notes for > > this version, i.e. > > That's an interesting idea. It would certainly be the easiest answer. > > I will mark this bug FIXED based on that solution. However, I don't have any way to actually implement the solution, so I guess marking "Fixed" was premature.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•20 years ago
|
Assignee: nparks → bugs
Status: REOPENED → NEW
Assignee | ||
Comment 9•20 years ago
|
||
link to website
Assignee | ||
Updated•20 years ago
|
Attachment #153792 -
Attachment is obsolete: true
Assignee | ||
Comment 10•20 years ago
|
||
Fixed br & trunk.
Status: NEW → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → FIXED
Comment 11•20 years ago
|
||
setting fixed-aviary1.0 for bugfixes checked into branch, for searching purposes. sorry for bugspam.
Keywords: fixed-aviary1.0
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → installer
You need to log in
before you can comment on or make changes to this bug.
Description
•