New issue template for customers wanting to report CDN issues with anaconda.org

[barabo]

Checklist

• I added a descriptive title
• I searched open requests and couldn't find a duplicate

What is the idea?

I propose that we point users to conda/infrastructure for reporting issues about CDN propagation delays (or other CDN issues). For this, I would suggest a new Issue template that required them to provide extra details that would aid with a response. We intend to integrate our monitoring to detect user-reported issues of this type so we can be proactive when they occur.

If conda/infrastructure is not the right place, I'm happy to request this from elsewhere.

Why is this needed?

When investigating CDN issues, extra details are often needed to quickly diagnose a user-reported problem. A new issue template could help responders act more quickly if those details were required.

What should happen?

I new issue template is created and made available from the New Issue template chooser in GitHub.

Additional Context

The new extra fields we would like to request are:

• The channel(s) affected
• When the problem was first detected
• Whether the problem concerns:
  • repodata completeness
  • package download speed
  • channel availability / accessibility
  • Other
• [optional] Example packages or URLs to investigate
• [optional] output of curl -I EXAMPLE_URL
• [optional] Urgency

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   - What OS and version you reproduced the issue on
   - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

[jezdez]

not stale