Skip to content

Development Philosophy

Michael Rees edited this page Jul 25, 2013 · 4 revisions

An overview of the release cycle and mission of WebWhirr.

Release Cycle

The goal of WebWhirr is to have three development streams: alpha, beta, and stable.

Alpha

Feature incomplete and unstable. Public snapshots will rarely be provided, although the source in the alpha branch will be updated accordingly. Within alpha, the purpose is to get code into a workable form resembling upcoming features, even if this does require sacrifices to be made with regards to code quality.

Beta

Feature complete. The focus on code in beta is to improve the overall quality, so code added and revised in alpha is refactored and maintained. Bug fixes are also made during this time.

Stable

The current release of WebWhirr. Code has been thoroughly tested, and should only be rarely updated.

Mission

The mission of WebWhirr is to eventually provide a fully featured, highly customizable web browser. Since this will obviously take some time, it is important to note that WebWhirr is primarily a learning tool. I am writing it to learn more about web standards and software engineering--and have enjoyed it immensely thus far.

Clone this wiki locally