This will keep Classic ongoing for as long as possible - but the success of this project will still rely on contribution. An organised, clear list of what security patches haven’t been fixedĪ fair warning will be presented to all those who want to use Classic, that it may be vulnerable to multiple security issues - but the choice is given to the user to proceed at their own discretion.Issues can be opened in a separate tracker, not getting closed for not focusing on G4.

Waterfox Classic will have its own simple landing page.GitHub Actions will be clearly segregated, allowing easy viewing of ongoing builds.

Contributors can clearly see what Classic development is ongoing.

This has the following benefits by not having two versions of Waterfox sharing resources:

To make sure the projects aren’t falling over each other, Waterfox Classic will now be moved out of the main Waterfox development repository and into its own separate repository - updating the previously archived “Waterfox Old”, now named Waterfox-Classic. Unfortunately, due to the rapid nature that the web is now expanding at, keeping Classic up to date with that is difficult. G4 has its eyes set to the future - a modern browser, focusing on modern web compatibility without sacrificing speed, or the balance of privacy and usability.Ĭlassic has focused on keeping the tried but tested available. Since Waterfox Classic and Waterfox Current (now G4) diverged, they have both have separate goals.

Waterfox Current G6.0.5 downloading