You can consider the security patches to be quite stable. They're not feature changes. They will go through the Alpha/Beta/Stable release process. Since we have source access, fixes can be made to them too. They're separated because the source code cannot be released yet. It's simply a choice for those who want that super early patching now that we have access to this material through our OEM partner.

I'm hearing: - pro: patches to known issues, early - con: added element of 'trust' since source code cannot be reviewed* (yet) I appreciate your responses, thank you. *not that I've ever done this myself, no aptitude for that; I'm already 'trusting the community' to alert us if something nefarious makes it into the code; among those in the community, I've already decided to trust the grapheneOS crew by installing it; therefore--if I'm being consistent--I have no reason not to opt-in

Patches' source codes will continue to be released on the months they are due to be released. If you wanted to get an early impression you'd need to reverse engineer and compare OS images with and without. Should be kept in mind that these patches are not for some new change from Google. They have and continue to release patches monthly and we'd put them in once they were released before. This is only available to us because now we have exclusive access. It's a bonus.