Screen Shots
Mailing Lists
Bug Reports




Whats new
Using Openbox

Openbox Features
Epist Features
The RC File
Menu File

Submitting a patch
What to do about a bug

There are 3 branches to Openbox's development. See below for each branch and a description of its purpose.


The Stable branch is (in theory) a bug-free version of Openbox. To get to this state takes a fair amount of testing and time, so it is also the most 'behind development' in its features.
The Stable branch is suitable for most average users.

The latest Stable release of Openbox is 2.2.3 (clear).
The Changelog for this release is here.


The Testing branch is where new development features come to be tested thoroughly before being released on the Stable branch. This means that this branch will be much closer to the current development of Openbox, but your chances of finding a bug also go up.
The Testing branch is suitable for more advanced users, users anxious for a new feature, and users who are willing to find bugs to help Openbox development.

The latest Testing release of Openbox is 2.3.1 (royal city).
The Changelog for this release is here.


The Development branch is only available via cvs. It is where all development on the Openbox project takes place, and can be very unstable at times.
The Development branch is recommended only for people who wish to participate in the development of Openbox.

Snapshots are taken against the Openbox cvs-tree every night, and the latest one can be downloaded here.

To stay completely up-to-date with development, you need to get the current tree directly from cvs.
Here are instructions for downloading the cvs-tree for Openbox:

cvs -d login
When prompted, use the password "anonymous".
cvs -d co openbox

You will now have an "openbox" directory which contains all of the newest code. To update this code base to stay up-to-date with changes in the Openbox cvs, you need to do this:

Go to the top directory of the openbox source code you retrieved from cvs.
cvs update -dAP
or, to get a clean tree, which will overwrite any changes you've made to the code, do this:
cvs update -dAPC

You can also browse the cvs repository. Be sure to check the branch you are viewing to be sure the files you are looking at are the ones you are interested in.

To submit a patch against the cvs-tree of Openbox, see here.