GBP team policies

[Pino Toscano]

Hi,

In data martedì 16 giugno 2020 19:04:21 CEST, Scarlett Moore ha scritto:
> I am trying to sort out gbp and have it working mostly now. However,
> I am also trying to comply with team policy and I now see I may have 
> messed up some of my repos:
> https://qt-kde-team.pages.debian.net/gitguidelines.html
> States no upstream in public space, does this include upstream and pristine-
> tar branches? This write up looks rather dated and doesn't include a workflow 
> for gbp. I am rather liking the gbp workflow so any advice is appreciated.

As also Lisandro wrote, we generally don't use gbp, and personally I
prefer to not use it:
- it makes the repository bigger
- since upstreams come with signing keys these days, the key is not
  stored inside the repo, so you still need to save files outside of it
  (and thus only the repo is not sufficient for the uploads)

You're right, that page might get an update, although from my POV the
basic idea (avoid upstream code) should still be there.

If you are maintaining an existing gbp repo, then please make sure that:
- the tags are signed
- not switch it away from gbp to debian-only layout, as it becomes a
  mess when browsing through its history
(As followup of the point above: please do not switch to gbp a
debian-only repository, for the same reason.)

-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20200628/dd11155e/attachment.sig>