In November 2002, a timeline was developed leading up to K-Meleon 1.0. One of the major questions is how we handle updates and major releases. In the past, updating the core and components files required so many changes that doing a mid-version upgrade was difficult, if not impossible, to do cleanly. However, if we can upgrade an existing release to use new Mozilla code, we might be able to do updates with every Mozilla release.
Updated: October 12, 2004
- Target major releases to every other major Mozilla milestone.
As the Mozilla roadmap was pushed back the release for 1.7, our calendar was adjusted accordingly.
- We had previously discussed offering updated plugins every 1.5 months. We have since dropped that idea since plugin updates didn't warrant this schedule.
- New plugins are made available as they are ready after appropriate testing and development.
- Between major releases, we should offer an update package that includes the new and improved plugins. It would help regular users stay current with K-Meleon.
- Because of critical bug fixes needed in K-Meleon 0.8, we wont really get onto the normal timeline until the release of K-Meleon 0.9.
- November 11, 2003: K-Meleon 0.8 released based on Mozilla 1.5.
- December 13, 2003: K-Meleon 0.8.1 released based on Mozilla 1.5.
- December 23, 2003: K-Meleon 0.8.2 released based on Mozilla 1.5. Service Pack for 0.8.1 installations also released.
Due to a slow development cycle on our part and a drawn-out development cycle for Mozilla 1.7, our schedule has been revised again.
- October 2004: K-Meleon 0.9 release based on Mozilla 1.7.4.
- January 2005: Upgrade package (K-Meleon 0.9.5. - Mozilla 1.8)
- April 2005: K-Meleon 1.0 release based on Mozilla 1.9
If we reach our 1.0 goals before April 2005, we would need to revise this schedule.