Branching & versioning packages policy

Modified Slind packages

repository::

clone of Slind

versioning::

.oi<N> added to the revision of package, resetting N every Slind package version change (e.g. 0.1-1.slind1.oi1, 0.1-1.slind1.oi2, 0.1-1.slind1.oi3, 0.1-1.slind2.oi1...)

working branch::

oi, tracking upstream (Slind) one.

process::

Upstream branch is merged to the oi as often as practical.

Native packages

repository::

created from scratch

versioning::

without oi or slind

working branch::

master

process::

Nothing special

Ported from Debian, not yet in Slind

XXX More info here XXX

repository::

created from scratch or cloned Debian.

versioning::

.oi<N> added to version, resetting N every Debian package version change.

working branch::

oi, synchronized with Debian package as often as practical.

process::

If Debian uses git for packaging, then it's repository should be cloned, and oi branches from it. If Debian package does not use git, new package releases should be pushed to git manually (or using git-buildpackage machinery).