Déjà Dup Project Policies

Release Schedule

Déjà Dup will follow GNOME's release schedule.


Déjà Dup uses a simple version scheme of just a major and minor number. The numbers correspond to each regular GNOME release (e.g. 17.5 was GNOME 2.31.5 and 18.0 was GNOME 2.32.0).


A best effort will be made to keep dependencies satisfiable on the most recent stable Fedora/Ubuntu cycle. Ideally longer.


There is a daily PPA built from trunk for testing.

Trunk Stability

  • Trunk should always remain buildable.
  • Trunk should always pass the test suite.
  • Any tagged release in trunk should correspond to a released tarball and be especially stable and coherent.

Code Reviews

All non-trivial branches need a code review.

Examples of trivial branches:

  • translation updates
  • test updates (new passing tests or fixups for existing tests)
  • documentation fixes
  • version bumps
  • build system changes

Examples of non-trivial branches:

  • normal bug fixes
  • features
  • refactors

Review Flow

  1. A branch will be flagged as ready-for-review in Launchpad for merging into trunk by developer A.
  2. A separate member of ~deja-dup-hackers -- developer B -- will review the branch.

  3. Once approved, developer A will merge into trunk if able. Else developer B will.

Feature Approval

All branches that introduce features or important UI changes additionally need approval from a member of ~deja-dup-team. This sign-off may implicitly come from either developer A or B above or explicitly from a third party C during the code review.

Apps/DejaDup/Policies (last edited 2013-10-09 21:52:45 by MichaelTerry)