Closed Bug 310099 Opened 20 years ago Closed 20 years ago

Update roadmap with new information

Categories

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

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: reed, Assigned: steffen.wilberg)

References

()

Details

Roadmap still states "September 2005" as release date for Beta 1. This should be updated to show the actual release date (from Help->About, I'm guessing 2005-09-08). @@ -153,7 +153,7 @@ <tr class="current beta"> <td>1.3</td> <td>Firefox 1.5 Beta 1</td> - <td>September 2005</td> + <td>2005-09-08</td> <td>Bugs</td> <td>Feature Complete general preview release</td> </tr> Simple as that. :)
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
-> Steffen
Assignee: bugs → steffen.wilberg
Beta 1 issue fixed 2005-10-02 15:24 by Steffen. The same thing applies for beta 2, though... Also, under "Structure" title: "We are planning for a Firefox 2.0 and 3.0, but will divide the planned work over (at this point) three major Milestones, 1.5 (September 2005), 2.0 (unscheduled) and 3.0 (unscheduled)." 1.5 date is wrong and the comma afer Milestones should be a colon. Also, the "Bugs" link for Firefox 1.5 is completely wrong. It checks for the Firefox1.1 milestone, fixed-aviary1.0, and some other stuff that's completely out of date.
Summary: Update Firefox 1.5 Beta 1 release date → Update roadmap with new information
I fixed the b2 release date and the bug link (Firefox bugs targetted to 1.5 and not having the keyword fixed1.8). I can't (and don't want to) give an estimate for the release date of 1.5 final.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Probably not. There's not much sense in tracking release candidates in the roadmap.
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
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.