|
Top-level
 Recent examples where we could have waited if we knew the release date in advance: August early ASB release: https://grapheneos.org/releases#2024080500 August monthly release: https://grapheneos.org/releases#2024080600 July early ASB release: https://grapheneos.org/releases#2024070200 July monthly release: https://grapheneos.org/releases#2024070201 3 comments
Fixing conflicts for the backports can take a lot of time and often requires very skilled work to do it properly as it will for one of the patches this month. Doing an extra OS release also takes a lot of our resources. It takes a lot of local compute time and testing effort. This shouldn't be something we need to spend resources on because we should know the official release schedule and should have early access. It's harming Android more than GrapheneOS since these kinds of artificial issues inflicted on us are exactly why we stopped contributing. |
Gregory's Server
For months with quarterly and yearly releases, it's common for our early ASB release approach to get those patches to our users days or even weeks early. However, the recent months where they released on Tuesday instead of Monday wasted our time without getting much from it.