On 2017-06-01 04:28, Jaromil wrote:
> On Thu, 01 Jun 2017, KatolaZ wrote:
>
>> 1) bugs reported on gitlab are forwarded to the bts, and any follow-up
>> on gitlab is reported on the BTS as well, so that we have a unified
>> history and a complete overview on the status of all issues, wherever
>> they are reported and whether they are linked to a specific package or
>> not.
>>
>> 2) bugs reported on the bts are followed up there, and might be caught
>> up on gitlab if they are assigned to a package, eventually. Sometimes
>> this is true, sometimes this is not true. Think for instance to bugs
>> for which there is no gitlab package...
>>
>> I agree that the BTS also needs some improvements, but nothing is
>> impossible, if we agree on the workflow. Having gitlab issues
>> automatically reported and followed up on the BTS will be relatively
>> simple.
>
> ok, lets at least try out the experience of the bts. I for one am not
> yet able to use it well. Was used to the 'bts' cli command which
> doesn't yet works so still need to figure out what to do via email and
> the headers are somehow confusing... we shall fork the devscripts then!
>
> ciao
>

And to add to the confusion . . . remember that gdo issues have been
imported to d1g (though it appears that function may be broken atm).

golinux