Making guake releases

This document describes a little policy that we follow to make releases of guake.

Code stability

After we see that guake code is ready to be released as a stable version, we will announce it in guake site and freeze all strings in guake to give some time to translators update their work.

Guake will not be released while critical or blocker bugs still open.

version numbering

We use three numbers to describe a Guake release, eg.: 0.2.2. See when each one should be changed:

• Major (0): When huge changes happens.
• Minor (3): Should be changed after impressive changes.
• Micro (1): After bug fixes and small changes.

Before releasing a new version, we will create a tag in git version control wich will be named with the new version number.

Translations

Translations can be considered small changes, so if a new translation is added, we can change only the Micro version number. Because translations don't change code stability.