[Pulp-dev] Tracking issues for plugin_template
bmbouter at redhat.com
Mon May 3 14:10:27 UTC 2021
I imagined for downstream Bugzilla for example, we would have the
downstream BZ link to the upstream using the tracker ggainey mentioned.
Then for the github issues we would have a 'Bugzilla' label, and the link
would be in the comments. I expect the scripts would ensure these were
present like they do today. So mostly we would need to update the scripts
(also like ggainey said). With this setup, searching in bugzilla would be
roughly the same to what it is today, and we could query on the label to
look at the big-picture and then find any bugzilla from any specific github
issue from the comments.
I don't think the external autolinks is that valuable since a regular link
is just as usable even if its longer.
On Fri, Apr 30, 2021 at 11:56 AM David Davis <daviddavis at redhat.com> wrote:
> Interesting. I did not know about this. Here's a link with more info:
> On Fri, Apr 30, 2021 at 11:34 AM Ewoud Kohl van Wijngaarden <
> ewoud+pulp at kohlvanwijngaarden.nl> wrote:
>> On Sat, Apr 24, 2021 at 09:21:05PM -0400, Daniel Alley wrote:
>> >On Fri, Apr 23, 2021 at 10:37 AM David Davis <daviddavis at redhat.com>
>> >> We started working on a plan to move repos over to Github Issues after
>> >> PulpCon last year but I think it kind of fell by the wayside over the
>> >> few months due to how busy we've been with stakeholder work. It would
>> >> definitely be a requirement in my mind to sort out things like how to
>> >> BZs to issues before moving plugins and other repos over to Gihub
>> >> that might have issues that affect downstream.
>> >I doubt there's any "good" way to link external bugs from Github because
>> >Mozilla doesn't do so. They just add an extra tag and you just have to
>> >find the link somewhere in the comments.
>> If you're on a paid plan you can replace links to an external system. I
>> can't find exactly where since it's hell to search for, but an example
>> can be seen in https://github.com/puppetlabs/puppet where PUP-NNN links
>> to their JIRA instance.
>> It looks like it doesn't replace it everywhere as can be seen in a
>> random PR: https://github.com/puppetlabs/facter/pull/2371
>> Certainly this isn't great.
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev