Closed Bug 207679 Opened 21 years ago Closed 21 years ago

Release Notes (1.1 ~ 1.4rc3) McAfee and Crescendo notes should be removed

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla_kl, Assigned: danielwang)

References

()

Details

- the entries for McAfee and Crescendo point to bugs which are WFM, so they can
go away
- all 4 Linux-Entries are pointless, as we have require glibc-2.2 now (as
written above in the "Software requirements")
missed a line: that all is for the block "compatibility information"!
"Double right clicking on a page can disable the keyboard. (Bug 70812)"

That's actually bug 30841, but it was fixed long ago.
> all 4 Linux-Entries are pointless, as we have require glibc-2.2 now
> (as written above in the "Software requirements")

Which relnote ver. are you referring to?
Blocks: 133795
Component: User → webmaster@mozilla.org
Product: Documentation → mozilla.org
QA Contact: rudman → malachi
Summary: Changes to relnotes → Release Notes (1.0~1.4) McAfee and Crescendo notes should be removed
Version: unspecified → other
at least 1.4RC1, I don#t exactly know, when the change was.
Blocks: 207595
-> me
Assignee: asa → stolenclover
Summary: Release Notes (1.0~1.4) McAfee and Crescendo notes should be removed → Release Notes (1.0~1.4rc3) McAfee and Crescendo notes should be removed
Looking at Mozilla 1.4 (the re-write looks great), I think this reference was
removed. I'm closing that bug anyhow.
Status: NEW → ASSIGNED
Summary: Release Notes (1.0~1.4rc3) McAfee and Crescendo notes should be removed → Release Notes (1.1~1.4rc3) McAfee and Crescendo notes should be removed
-> fixed
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Summary: Release Notes (1.1~1.4rc3) McAfee and Crescendo notes should be removed → Release Notes (1.1 ~ 1.4rc3) McAfee and Crescendo notes should be removed
Product: mozilla.org → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.