[Pkg-opennebula-devel] repository layout / git workflow

[Dmitry Smirnov]

On Wednesday 05 August 2015 14:24:23 Olivier Berger wrote:
> [1] https://wiki.debian.org/Teams/pkg-opennebula/GitWorkflow

My favourite _Branching policy_ is written down in the Git guidelines of the 
Debian KDE Team [1]:

    Debian packaging branches must not contain original source and must not
    have been merged with a branch containing original source code (referred
    by name "upstream" in the rest of this document) in any point of their
    history. If necessary, it is recommended to keep a private upstream
    branch in the private local repository or just track upstream remote Git
    repository locally. Debian packaging branches must only contain debian/
    subdirectory in their root directory in order to avoid potential
    conflicts with upstream source. This restriction applies even to Git-
    specific files like .gitignore.

Such policy is wise for heavy packages like "calligra" which contains over 
24000 files (including few non-free ones).

Debian KDE package repositories are lightweight, not contaminated with non-
DFSG files and have no worthless history of upstream releases since beginning 
of time...

What if we consider using the same practice?

[1]: https://pkg-kde.alioth.debian.org/gitguidelines.html

-- 
Cheers,
 Dmitry Smirnov.

---

Perhaps is is better to be irresponsible and right, than to be responsible
and wrong.
        -- Winston Churchill
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-opennebula-devel/attachments/20150809/44faa7cd/attachment.sig>