Conversation

Replying to
Releases go through internal testing, then Alpha, then Beta, then finally to Stable. If any significant issue is found, it doesn't reach the next phase of testing. The releases are still all production releases and we usually intend for every release to reach Stable.
1
8
Replying to
Internal testing is mostly done while finishing up builds, generating deltas, etc. It rarely adds much of a delay since we generally release for all devices at the same time and it takes a long time to build, etc. 1-2 hours in Alpha before Beta, 12-72 hours in Beta before Stable
1
1
Currently use both a recent Ryzen 9 5950X workstation and a much older Broadwell-E i7-6950X workstation for the official GrapheneOS builds. It takes over 2x as long to do a build on the older workstation. That older workstation had a proper workstation class CPU but it's old now.
1
1
Newer workstation is a high end desktop CPU because I wanted to do a Zen 2 Threadripper build but couldn't get the parts in Canada. Ended up wanting to wait for Zen 3 Threadripper which has been indefinitely delayed and may never be released. It's mostly about availability/time.
1
1
I have 1Gbit download / 720Mbit upload fiber to my condo. Could be upgraded one level but their standard modem/router combo they force you to use will be a bottleneck since it only has gigabit Ethernet. Also not sure what class of Ethernet cables are in the walls of the condo.
1
1
The main way to improve upload time would be making the sync more sophisticated than doing rsync to each server 1 by 1. For example, it'd be faster to upload to one of the EU servers and then sync from there to the others. Build time is also main time sink for releases not that.
1
1