Path: csiph.com!news.redatomik.org!weretis.net!feeder4.news.weretis.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Moving off of git-dpm (Re: git-dpm breakage src:faker)
Date: Tue, 31 Jan 2017 21:00:02 +0100
Message-ID: <t5MKS-4Js-11@gated-at.bofh.it>
References: <t4J2G-6LR-9@gated-at.bofh.it> <t4JP4-7iL-23@gated-at.bofh.it> <t5MhQ-4zG-7@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
User-Agent: KMail/4.13.3 (Linux/3.13.0-106-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Approved: robomod@news.nic.it
Lines: 33
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:9208

On Tuesday, January 31, 2017 02:23:29 PM Barry Warsaw wrote:
> On Jan 29, 2017, at 09:39 AM, Brian May wrote:
> >I would think "gbp pq" is the most popular.
> 
> I've used it on some of my non-team packages and while it takes a little
> getting used to for the standard git-dpm workflow, it's been mostly fine.
> 
> What I'd really like to see is a page like
> https://wiki.debian.org/Python/GitPackaging for a non-git-dpm workflow. 
> (The page itself could probably use a bit of gardening anyway.) 
> Specifically, I'd like to see guidance on any tasks which are different for
> git-pq (or non-git-dpm as the case may be).
> 
> I'd suggest cloning that page instead of modify that page to cover both
> cases.  Edit the clone as if it were the opinionated view of just using gbp
> tools and gbp-pq.  The page should also have instructions on
> opportunistically switching away from git-dpm.
> 
> Then we can start to use those instructions in anger and add any other
> recommendations for corner cases.  Once we have enough experience with
> gpb-pq throughout the team, we can consider making an official switch.

We should probably be thinking in terms of post-release for this change.  
During the pre-release freeze, the release team doesn't typically allow 
changes that extraneous to fixing the specific issue they are letting a 
package into Testing to fix.  The .git-dpm file is shipped in the package, so 
if we drop git-dpm, we're going to have to deal with getting .git-dpm removals 
through the release team for any package that needs update during the freeze.

That will also give us time to make sure we have a proper migration strategy 
and sufficient documentation.

Scott K