[gentoo-dev] RFC: Should the bot add PRs directly to TRACKER tickets?

[gentoo-dev] RFC: Should the bot add PRs directly to TRACKER tickets?

[Jonas Stein]

Hi,

sometimes there are PRs assigned to a TRACKER.

On the one hand it makes sense to reduce the work of creating a separate
ticket per package.

But on the other hand the TRACKER ticket will get chaotic and noisy.
It will also happen some day that someone adds Closes: $TRACKER_TICKET

We would not add patches for a specific package to a TRACKER too, but to
a separate ticket, which is linked to the TRACKER.

Any good ideas?

Here is an example:
https://bugs.gentoo.org/683184
In this case it is still quite tidy, but other TRACKERS will become
unreadable by that.

-- 
Best,
Jonas

Re: [gentoo-dev] RFC: Should the bot add PRs directly to TRACKER tickets?

[Kent Fredric]

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

On Sat, 26 Oct 2019 14:24:22 +0200
Jonas Stein <jstein@gentoo.org> wrote:

> Here is an example:
> https://bugs.gentoo.org/683184
> In this case it is still quite tidy, but other TRACKERS will become
> unreadable by that.

I think in that case the PR bot should tell people:

- Find / Open the relevant bug
- Link to that instead
- Perform the dance required for the PR bot to recheck things.

And otherwise reject citing a tracker as a close/bug source in a PR.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-dev] RFC: Should the bot add PRs directly to TRACKER tickets?

[Thomas Deutschmann]

[-- Attachment #1.1: Type: text/plain, Size: 898 bytes --]

Hi,

I don't understand your mail or call to action, sorry :)

The bot looks for GLEP 66 tags using simple regex. The only purpose of
the bot is to link found contribution (in this case a pull request) to
bugs on b.g.o to inform assignee about contribution which happened
somewhere else in case assignee isn't using/following GitHub for example.

That's all.

Bot doesn't understand bug type and it would be overkill to make bot
understand bugs.

In the example bug, https://bugs.gentoo.org/683184, the problem was that
no individual bug per package was created. So people changing packages
to address the issue raised in tracker bug used that bug as reference.
In other words: The initial failure was that no individual bugs per
affected package was created...


-- 
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]