Branching & versioning policy

Packages based on Debian

If OpenInkpot package closely follows Debian one, only minimal necessary changes are introduced and resynchronization takes place often, then it is based on Debian.

There should be no such packages in OpenInkpot, they should be part of  IPlinux instead. See the  IPlinux policy.

IPlinux packages

IPlinux packages should be used "as is" without changes.

If some change is required in IPlinux package for OpenInkpot, then it should be done there in generic manner.

Native OpenInkpot packages

If package does not exist in IPlinux and it makes little sense to add it there, then it should be developed as a part of OpenInkpot.

Repository

OpenInkpot packages must reside in git repository git.openinkpot.org.

The following repository layout is recommended:

• upstream branch tracks either
  • Upstream tarballs, imported using git-import-orig, or
  • Upstream version control system, converted or fetched,
• master branch contains source code for OpenInkpot package (zelazny branch)

If older OpenInkpot branch needs a bugfix, then git branches are created:

• asimov is for fixing bugs in stable branch asimov,
• ...

Package versioning

OpenInkpot packages are versioned as in Debian, without extra suffixes.

• If package is imported from Debian, it should increment revision of Debian package.
• If package is created from scratch, it should use revision 1 in first release.