Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Sandro Tosi <morph@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: How to maintain multiple branches (sid/bpo/exp etc)?
Date: Tue, 03 Nov 2015 01:10:02 +0100
Message-ID: <qqxkK-3Fq-19@gated-at.bofh.it>
References: <qqviW-2bx-17@gated-at.bofh.it> <qqviX-2bx-23@gated-at.bofh.it> <qqwoF-34I-3@gated-at.bofh.it> <qqx1o-3iZ-9@gated-at.bofh.it>
Old-Return-Path: <sandro.tosi@gmail.com>
MIME-Version: 1.0
Sender: robomod@news.nic.it
Content-Type: text/plain; charset=UTF-8
Approved: robomod@news.nic.it
Lines: 28
Organization: linux.* mail to news gateway
Xref: csiph.com linux.debian.maint.python:7825

> Raphael can probably say more about this, and advocate for DEP-14, which in
> your case probably makes more sense than I have:
>
> http://dep.debian.net/deps/dep14/
>
> It's probably worth some experimentation to see if DEP-14 is the right
> approach for you, and how that might inform updates to DPMT policy at some
> point.  Just remember to document it in README.source. ;)

yeah I think DEP-14 is the right approach here, but it has 2 drawbacks:

1. I have a simple package, which I keep maintaining with the usual
'master' and 'upstream' branches, but then the testing freeze will
come and I want to start uploading to experimental, at that point I
need to change the layout of the repo (annoying, but I am the
maintainer, I can do that I guess)

2. what if I am not the package maintainer tough? I cannot enforce a
new layout to that repo. take this real-life example sqlalchemy: I
asked Piotr for a jessie backport of 1.0.8, he agreed I can go ahead,
I have a package ready and I dont know how to commit it to the repo.
what should I do at this point?

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi