RE:Streamlining the use of Salsa CI on team packages

To: Thomas Goirand <zigo@debian.org>, "debian-python@lists.debian.org" <debian-python@lists.debian.org>
Subject: RE:Streamlining the use of Salsa CI on team packages
From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>
Date: Mon, 14 Oct 2019 13:51:57 +0000
Message-id: <[🔎] A2A20EC3B8560D408356CAC2FC148E53017D80D2F5@SUN-DAG3.synchrotron-soleil.fr>
In-reply-to: <[🔎] 257c2998-e0cc-96ec-cd0b-9f488ed40a4d@debian.org>
References: <3429cc8e-87d4-facc-870d-1e664fe0779f@debian.org> <e74f9fd5-a16d-0dc6-93a1-5ba3b699a392@debian.org> <20e70d22-ebc3-f0ae-818b-4d8ba7f7f88f@at.or.at>,<[🔎] 257c2998-e0cc-96ec-cd0b-9f488ed40a4d@debian.org>

Hello,

and if at the end the upstream could take care of the Debian packaging, by adding a 
.salsa-ci.yml in the upstream directory, in order to have a feedback with nice badges ?

Cheers

Reply to:

Follow-Ups:
- Re: Streamlining the use of Salsa CI on team packages
  - From: Peter Pentchev <roam@ringlet.net>

References:
- Re: Streamlining the use of Salsa CI on team packages
  - From: Thomas Goirand <zigo@debian.org>

Prev by Date: Re: Python2 removal: package with low-popcon reverse dependencies
Next by Date: Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream
Previous by thread: Re: Streamlining the use of Salsa CI on team packages
Next by thread: Re: Streamlining the use of Salsa CI on team packages
Index(es):
- Date
- Thread