[pkg-php-pear] debian- and upstream- branches (Was: ITP: php-symfony-process -- Symfony PHP Framework - Process component)
david at tilapin.org
Thu Jul 4 21:19:21 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Le 27/06/2013 22:14, Thomas Goirand a écrit :
> On 06/28/2013 07:51 AM, David Prévot wrote:
>> Le 27/06/2013 18:49, David Prévot a écrit :
>>> Le 27/06/2013 18:35, andrea rota a écrit :
>> - Why differ from the usual gbp workflow with debian-sid/upstream-sid
>> instead of master/upstream?
> master/upstream is IMO bad: "master" doesn't express anything, and gives
> no clue what the branch is for.
Well, since it’s a Git repository for Debian packaging, I’d assume the
master branch contains the Debian package (i.e. matches the default gbp
> Also, we don't only track the Sid branches, but also what's in stable
> and old stable. Once the stable is released, we create: debian-wheezy /
> upstream-wheezy. On many packages, we also have debian-squeeze /
> upstream-squeeze too.
It seems useless to enforce creating those branches if we don’t need
them: IMHO, debian-wheezy (or debian-squeeze, or debian-jessie, etc.)
should only be needed once and if it differs from the main master or
debian-sid branch, in order to prepare a stable or security upload.
upstream-wheezy (or upstream-squeeze…) should not ever be useful in any
Here is a proposed wording to update the current advice :
There is no need to create *-wheezy or *-squeeze unless your
package reached these distributions,
There is no need to create *-wheezy or *-squeeze unless a
package needs to be updated in any of these distributions,
either via an (old)stable or a security upload,
>> - Why impose an export-dir? Isn’t this part of workflow better suited in
>> one ~/.gbp.conf for those who care?
> Because the default of gbp is simply bad, and this helps newbies (we
> have a lot of people coming and going in the team).
Well, you still can help newbies in advising them to add the export-dir
option into their own ~/.gbp.conf. Enforcing it to anyone working on
these packages is likely to breack their own workflow, or default third
party packages settings (e.g. debi).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the pkg-php-pear