ITT: People making assumptions based off the tagline without reading the article
Basically not much changes, they’re just gonna wait to post their code until it’s done instead of letting it be viewed in progress
That’s a huge change. Reviewing one years’ worth of code at once is practically impossible, this significantly reduces the chances of a third party spotting malicious changes in the code.That’s already how it functionally worked for each major release
Here’s their previous strategy: https://web.archive.org/web/20220917195332/source.android.com/docs/setup/about/codelines
Google works internally on the next version of the Android platform and framework according to the product’s needs and goals
When the n+1th version is ready, it’s published to the public source tree
The source management strategy above includes a codeline that Google keeps private to focus attention on the current public version of Android.
We recognize that many contributors disagree with this approach and we respect their points of view. However, this is the approach we feel is best and the one we’ve chosen to implement for Android.
As far as I can tell, this would really only affect QPRs, since the public experimental branches that get made after they throw the next release over the wall is going away
oh, got it, thanks. feel so bad about people having read my incorrect comment haha
Meh, reasonable. Thanks for posting the clarification.
It’s not like Android is especially open to drive-by contributions anyway. I don’t think really changes much for the downstream consumers of the releases.
It means my GrapheneOS updates will probably be a little slower.
And yet Graphene will still probably need more private and secure
now I’m less worried about goggle being required to sell android. this way it does not matter anymore
Why would you think it doesn’t matter?
we were worried about android being sold off because of what bad things the new owner would do with it
time to switch to graphene or e/os?
graphene is a fork of stock android, so wouldn’t this affect them?
Yes. This hurts the GrapheneOS project. It won’t stop the project, but it makes their work harder.
