mozilla / releasehealth Goto Github PK

For the blocking bugs at https://lmandel.github.io/ReleaseHealth/?channel=aurora, I should be seeing this bug right now: https://bugzilla.mozilla.org/show_bug.cgi?id=1242641 But it isn't listed. I suspect that might be because you're checking the overall status of the bug rather than status-firefox46.

STR:

1. Visit https://mozilla.github.io/releasehealth/
2. Right-click the Firefox logo in upper-left corner.
3. Choose "View Image"

ACTUAL RESULTS:
I'm taken to...
https://mozilla.github.io/releasehealth/images/firefox-beta.png
...which is higher resolution than my monitor (2485 x 2340 pixels).

EXPECTED RESULTS:
Image should be an order of magnitude smaller, so that it's closer to the right size that it ends up on-screen, and so it can be downscaled (if needed) more efficiently.

(The <picture> element might help here, too, if we want to be really fancy and provide different images for different resolutions.)

This manifests in the real world as the image having a noticeable delay before it displays on first pageload, as well as on tab-switch.

It'd be nice if we didn't include FIXED bugs in the counts (or queries) for nightly since once something is fixed there we don't need to uplift anywhere. I could write a patch but it'd end up with some ugly if {...} blocks.

STR:

1. Visit https://mozilla.github.io/releasehealth/ in Firefox.
2. Before the "?" regression-counts have populated with numbers, clear your cache (Ctrl Shift Del on Linux -- or, in History menu, choose "Clear Recent History").
3. Accept the defaults ("last hour" should be selected, & "Active Logins" must be checked)

ACTUAL RESULTS:
2-3 "error" alert boxes appear in quick succession.

EXPECTED RESULTS:
No such alerts; possibly text on the page telling me to reload, if necessary.

We should have page titles to the queries and maybe also get them to open in new tabs instead of being regular links

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)

We have a new nightly icon now

The dashboard (displayed in all our offices) gives us a view of the train model but we now have projects that are not necessarilly relatef to a specific train. Trailhead was a dot release, Skyline will be in 70 but a lot of the work will be uplifted directly from beta. We need to extend the dashboard with temporary project views.

Let's start with Skyline.

The Release logo is still the old pre-quantum one and is also flashing on each click to the beta and nightly channels. Images are also in PNG format but we have all these images in SVG format which is lighter and can be resized without quality loss.

If relman has minused an issue from tracking, ie marked a regression as tracking-firefox{version}: - , then we should exclude those bugs from the release health dashboard. (as they currently are excluded from the Platform triage wiki queries) This way, we have at least one way to exclude minor regressions and edge cases from what we need to pay attention to.

A new Nightly log landed in the 70 cycle and the 70 beta cycle is starting. Let's update our Nightly/Beta logos on the dashboard.

Hey, if I leave this open in a tab, the information in it has gone stale after a while and is no longer accurate. To fix that I can of course reload the page. It would work much better as a "always up on screen" sort of page if it would refresh itself, possibly even more smarter than just at a fixed interval.

Opening this issue so as that we don't forget to remove Skyline code after the project has ended (but keep improvements we added to the dashboard with the skyline view, not just revert the commits).

Discussed with the relman team today, we'd like to have a 'Fixed bugs' for the skyline view added to show progress.

There is no README and while refactoring the code yesterday, I discovered that there is at least one thing that should be documented, the display=bigscreen option.

STR:

1. Open http://mozilla.github.io/releasehealth/
2. Resize window to 1280x1440.

Expected results: a pretty dashboard
Actual results: an unreadable mess

.

We don't need to triage an issue again in the engineering/relman regression triage meeting, if it has a priority set already of P4 or P5.

I also think we can exclude issues with the "stalled" keyword, which means it's already been triaged and investigated to the point where we don't see further possible action, but don't want to close the bug.

We could consider excluding assertion bugs, if they aren't sec-high or critical. We get maybe 30 a week. They usually aren't urgent to fix, and people don't feel driven to figure out if older branches are affected.

STR:

1. Visit https://mozilla.github.io/releasehealth/
2. Click "Fork me on github" in upper-left.
3. (optional) Hover the "fork" button, & try to figure out how to file an issue.

ACTUAL RESULTS:

• You're taken to lmandel's fork of releasehealth (which is forked from mozilla/releasehealth, which seems to be the official repo).
• If you hover the "fork" button, it shows that you'll end up forking lmandel's fork (I think) instead of the upstream official repo.
• There's no way to file an issue (because you're looking at a fork)

EXPECTED RESULTS:
The link should point to the official mozilla repo of releasehealth, so that people will end up forking that and will be able to file issues etc.

It was showing new regressions, with status-firefox69 = unaffected and status-firefox70 = affected. Those should only be showing up as "new".

Github supports a URL in the repo metadata and it would be nice if it pointed to https://mozilla.github.io/releasehealth/ to flip back and forth from the code to the live site.

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

We can mark these fix-optional to exclude them, but I'd also like to not display issues I already know we decided not to track.

https://mozilla.github.io/releasehealth/ is broken because https://product-details.mozilla.org/1.0/firefox_versions.json is not sending CORS headers:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://product-details.mozilla.org/1.0/firefox_versions.json. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Can you exclude anything marked meta in the summary or whiteboard from the p1 and untriaged queries?

And, best to also exclude anything that isn't marked status-firefox70: affected or ---

Thanks!

Maybe we could remove <div id="diag"> or instead add more angle.

Previous version displayed on an office monitor:

Current one:

It would be nice to have a favicon for this page so that it shows up in pinned tabs.

The two regression bug queries include &resolution=--- but the status flags are the source of truth about the fix on the specified version and are already part of the query. This means that a regression bug affecting all branches will disappear from the count when it's fixed on Nightly-only. IMO it should only be removed when it's uplifted as uplifts aren't necessarily immediate (e.g. the author may be asked to rebase).

In summary, I think &resolution=--- should be removed from the two queries to be more accurate about the state of the release (which is what the dashboard is all about IIUC).

Product details provides the current versions of Firefox:
https://product-details.mozilla.org/1.0/firefox_versions.json
To avoid such commit:
15331f6

I tried to upload the new one but got this:

Uploads are disabled.
File uploads require push access to this repository.

File can be found here - mozilla/whatthetrain@fbe5e79

This Mozilla repository has been identified as lacking a license. Consistent with Mozilla's Licensing Policy an open source license should be applied to the code in this repository.

Please add an appropriate LICENSE.md file to the root directory of the project. In general, Mozilla's licensing policies are as follows:

• Client-side products created by Mozilla employees or contributors should use the Mozilla Public License, Version 2.0 (MPL).

• Server-side products or utilities that support Mozilla products may use either the MPL or the Apache License 2.0 (Apache 2.0).

In special cases, another license might be appropriate. If the repository is a fork of another repository it must apply the license of the original. Similarly, another license might be appropriate to match that of a broader project (for example Rust crates that Firefox depends on are published under an Apache 2.0 / MIT dual license, as that is the dual license used by the Rust programming language and projects).

Please ensure that any license added to the LICENSE.md file matches other licensing information in the repository (for example, it should match any license indicated in a setup.py or package.json file).

Mozilla staff can access more information in our Software Licensing Runbook – search for “Licensing Runbook” in Confluence to find it.

If you have any questions you can contact Daniel Nazer who can be reached at dnazer on Mozilla email or Slack.

OPENLIC-2023-01