[pkg-php-pear] debian- and upstream- branches (Was: ITP: php-symfony-process -- Symfony PHP Framework - Process component)

[David Prévot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

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
scheme).

> 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
usual scenario.

Here is a proposed wording to update the current advice [0]:

From:

	There is no need to create *-wheezy or *-squeeze unless your
	package reached these distributions,

To:

	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,

	0: http://pkg-php.alioth.debian.org/

>> - 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).

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJR1ebYAAoJEAWMHPlE9r085pMIAICoh4+w8cVl3hQZLNk6Tdft
YggYQKsZjMkeJK4xV3ISVENhwmNXwejfxZS7AfTr0LSCaKDloacGEDxxTb8FFjLs
gYtGOQNDBh8UzdiuPs5Q/h6fSS080Pw7aehQ0TssKiktIsPXUpRXenKFF/1flObm
zvPVYDLIZ8NRrXOgZ7Z3ygHCP4wRspIhGIftV1qaIzX+Snk6jWHRKwv7hW09UV+g
bJ6HEwwS7x+xPBWJU9dijPiHRbnEDnQQ1tcrnYwkiT4zv0zd/OCxDZrYGIpU0O26
amFWqoYi8V2FRRlY2LJRBFmwRLaT/VKDBXnEP31utUr3f3rCGheBqGwHZz/Kqvk=
=w/Qs
-----END PGP SIGNATURE-----