When performing the initial page load for a repo, TBPL loads at most 10 pushes, however this is also limited to only pushes that were made within 24 hours of the most recent push. ie: there can be between 1 and 10 pushes shown. I'm not convinced this is the best algorithm, but showing fewer pushes does have the benefit of hiding old pushes that are no longer of interest (until the user presses the down arrow) - clearing them mentally out of the way, and also ensuring it's clear to the user that they are older - and so previous issues can be ignored (eg in the case of mozilla-release, the older pushes are often for the now EOL version of Firefox, since an uplift has taken place; or in the case of a rentable repo where the old results were from the previous person borrowing the repo). For treeherder we could go with something simpler: * Show at most 10 pushes (no change from present) * However do not show pushes in the initial pageload whose push time is more than N hours ago; with the exception that we must return at least one push. I would suggest an N of 24-48 hours. CCing :sheriffs for thoughts.
To be clear: TBPL uses "N hours prior to time of last push", whereas for treeherder I'm proposing "N hours prior to current time, but at least one push" - and also I think we could raise N from TBPL's 24 to say 36.
4 years ago
Priority: P3 → P5
I don't think there's a desperate need for this.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.