chore: enable stale bot for issues

[v1v]

What

Enable stale bot to notify and then close the Issues that haven't had any activity for 120 days, a notification will be sent after 100 days and if nothing else happens they will get closed 20 days later.

How it works

• Support issues only as stated
• It uses the Stalled label to categorise the ones that have been informed without any activity in 120 days.
• It looks for the issues that got the label discuss and question.
• Those Stalled issues will be closed if no further activity after 20 days.
• Those issues without a label are excluded from the bot. (There is no support for such). The workaround will be as simple as label them with Stalled then the bot will close them after 20 days.

Issues

Closes #912
Relates to elastic/beats#19157

Questions

@cachedout what do we do to enable the botelastic to work with this repo? I'll ask infra to enable it

[vigneshshanmugam]

This feels really long IMO, how about 3-6 months? Cleanup sooner also ensures we are picking and working on backlogs at some point. just a personal preference though? @jahtalab thoughts?

[v1v]

Sure thing, I just took what we got in place as a template, happy to change it :)

[hmdhk]

I agree, we should make a decision about an issue within 3-6 months (possibly even sooner than that but to reduce noise let's set it at 4 month). We either close the issue or add an appropriate label (e.g. bug, enhancement) to it.

[apmmachine]

📦 Bundlesize report

Filename	Size(bundled)	Size(gzip)	Diff(gzip)
elastic-apm-opentracing.umd.min.js	61.7 KiB	19.6 KiB	💚 0 Bytes
elastic-apm-rum.umd.min.js	55.7 KiB	18.2 KiB	💚 0 Bytes

[apmmachine]

💚 Build Succeeded

Expand to view the summary

Build stats

• Build Cause: [Pull request #914 updated]

• Start Time: 2020-10-08T10:36:22.308+0000

• Duration: 79 min 23 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1028
Skipped	10
Total	1038

Steps errors

Expand to view the steps failures

• Name: Error signal

  • Description: The test failed

  • Duration: 0 min 0 sec

  • Start Time: 2020-10-08T11:14:26.401+0000

  • log

[hmdhk]

Thanks @v1v,

I think the condition for the which issues should be considered stale is not correct. We want issues with question, discuss labels to be considered stale. Also issues with no label should be considered stale as well.

But issues with any other label should be exempt from being stale.

[hmdhk]

I agree, we should make a decision about an issue within 3-6 months (possibly even sooner than that but to reduce noise let's set it at 4 month). We either close the issue or add an appropriate label (e.g. bug, enhancement) to it.

[hmdhk]

I think these two sets of labels are should be reversed.

[v1v]

Aha! I actually read the description in the issue incorrectly! Thanks for the heads up :)

[vigneshshanmugam]

LGTM