mozilla / mozilla/probe-scraper

always set bugs created for expiring probes as tracking and affecting the current Nightly version

Open
#805 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
26
Forks
73
Avg merge
10h
Merged PRs (30d)
3

Description

When the probe-scraper files a bug for an expiring probe, it should set it to always

  1. be tracked for the current Nightly version because each unresolved bug will cause a test failure since https://bugzilla.mozilla.org/show_bug.cgi?id=1918242

  2. only affect the current Nightly version and set other Firefox status flags to unaffected.

  3. This means the flag shown e.g. as tracking-firefox132 (technically, it's cf_tracking_firefox132) should be set to +. By default, it's only possible to request tracking (?) but Release Management would approve every bug because of the looming test failure. Release Management (Dianna, Donal, Pascal and Ryan) or dkl from bugzilla.mozilla.org can help with getting the permission for the bot.

  4. cf_status_firefox132 should be set to affected, all other available cf_status_firefox* flags to unaffected.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the probe-scraper code that files bugs for expiring probes and inspect how Bugzilla tracking and Firefox status flags are currently set. Verify how the current Nightly version and available cf_status_firefox* fields are determined. Done means these bugs receive approved tracking for the current Nightly, affect only that version, and mark other available Firefox status flags unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.