UI: Hide stable builds #5
No reviewers
Labels
No Label
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-buildbot-www#5
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "pablovazquez/blender-buildbot-www:ui-hide-stable-builds"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
They were exposed mainly so release maintainers could keep an eye on
them. This is no longer necessary since we have an API for it at:
/?format=json&v=1
e.g. https://builder.blender.org/download/daily/?format=json&v=1
Hide these in all environments (LOCAL, UATEST, and PROD).
Hiding Stable releases is something that is coming up every now and then. The downside of this is that it is harder to grab the build without going to some deeper depths of the system. It might be OK, but is something for Thomas or Phillipp to sign off on.
The side effect of that would be that right after a release, the Blender version will disappear from the list. I am not sure if that is really that more clear.
The Release Candidate is not to be hidden. That effectively makes it impossible to test blender at bcon4, and makes it impossible for people to test builds after some commits are landed as part of LTS, before the LTS has been released.
Hiding stable and going via the API / JSON is fine for me.
The Release Candidates should be kept, but they are still on the screenshot so I assume that was a mistake in the title.
UI: Hide stable and release candidate buildsto UI: Hide stable and buildsUI: Hide stable and buildsto UI: Hide stable buildsThey are not hiding now, Pablo updated the patch as i was typing I think.
From the code side it seems fine to me!
Yes, my bad. Initially I hid them but then realised how silly that was and fixed the code but forgot to update the title.