As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

They're pulled down automagically and show as untracked files.

[email protected] is no longer active, we should stop mailing that address on all telemetry alerts.

I usually end up looking at the evolution view dashboard to check out any regressions.
Can we get a direct link to it in the mail?
Currently getting there requires a lot of steps: click link in mail -> find and click link to get to distribution view -> click evolution view -> wait for loading...

Just because someone changed the shape of a probe doesn't mean all regression detection should fail.

Consider number of errors / number of migrations. If this stays constant, everything is okay. However, number of errors can go up (with no regression), as long as number of migrations go up as well. Similarly, number of migrations might regress down.

We can't necessarily look at them separately, because that could lead to false positives and false negatives (if they moved in separate directions).

We could solve this in a few place:

1. A new ping at the browser
2. In the aggregates dataset
3. Here

Details here: https://circleci.com/gh/mozilla/cerberus/41

Error:

Traceback (most recent call last):
  File "alert/expiring.py", line 279, in <module>
    main()
  File "alert/expiring.py", line 244, in main
    if sys.argv[1] == "test": run_tests()
  File "alert/expiring.py", line 177, in run_tests
    assert len(get_release_dates()) > 4 # this function should return several versions if the table is formatted correctly
  File "alert/expiring.py", line 98, in get_release_dates
    result.update(get_version_table_dates(table))
  File "alert/expiring.py", line 50, in get_version_table_dates
    if "Firefox" not in field.string:
TypeError: argument of type 'NoneType' is not iterable
Exited with code 1

This can be verified by running python alert/expiring.py test. Result:

Traceback (most recent call last):
  File "alert/expiring.py", line 279, in <module>
    main()
  File "alert/expiring.py", line 244, in main
    if sys.argv[1] == "test": run_tests()
  File "alert/expiring.py", line 177, in run_tests
    assert len(get_release_dates()) > 4 # this function should return several versions if the table is formatted correctly
  File "alert/expiring.py", line 93, in get_release_dates
    table = soup.find(id="Future_branch_dates").find_parent("h2").find_next_sibling("table")
AttributeError: 'NoneType' object has no attribute 'find_parent'

Seems as though something happened then which may have caused problems