Cutting a release (and publishing) does cost significant time and effort. You effectively need to code-freeze, get all code merged into main, run all tests and QA, fix any breaking bugs, compete signoffs etc. On some of our small projects, doing a release could burn up to 2 weeks of real time, which on a monthly release cycle was killing us.
So I can almost buy their reasoning. But otherwise, agree that they can’t be trusted, and releasing once a quarter doesnt seem that hard.
Do you have a source for that? I can believe that select OEMs are getting preview internal access, but I strongly doubt they are releasing with ROMs cooked from those internal branches. That would open the OEMs to GPL requests/violations. And internal access doesnt mean doing the release processes that chew up time.
Giving preferential treatment to certain OEMs is its own issue though, but its a anti-competitive behaviour issue rather than a licencing issue.
I was overly vague, and “Android” means different things in different places. I usually say “AOSP” for Open Source Android and “Google Android” for open core Android. This also isn’t quite accurate.
AOSP is basically a repo, not a ROM, not an OS, not even code (technicaly). This has always been pushed to on “release”, not during development.
Google has it’s own (private) repos for development. I suspect some OEMs have access to HEAD.
Google used to publish device code for Nexus/Pixel devices. This stopped in 2025. This was separate to AOSP, but would build with AOSP for “Android Android” or “Open Source Android”. Some people would “add gapps” to get closer to “Google Android”.
Kernal code from Google for Pixel devices is still publically available as is required by the GPL. Basically no other part of Android is GPL and has this requirement.
A “release” pushed to AOSP used to basically line up with a Nexus/Pixel update. At the end of 2025 they changed it to 4 times a year, now they are changing it to twice a year.
“Android Security Bulletin” is a different thing, OEMs get early access to it. Everyone else gets delayed releases by about a quarter. This delay was new in 2025, this will continue to happen.
Google isn’t giving built ROMs to OEMs, even if it was, assuming it’s internal only, it wouldn’t be a GPL violation. AOSP has never distributed built ROMs.
Of course. Although I can kinda see why they dont want to do that either. All the fly-by-night OEMs would be using dev and shipping half-baked ROMs (which I guess they do anyway, but it would be worse).
So just push everything to open source then, not only releases but branches? Nobody forces you to have fast release schedule, but you either open source or you are not. Releasing sources 2 times a year is not an open source.
Actually, it is open source. There is nothing wrong with developing in private and pushing public when its done. Every developer works that way to some degree or another. And there are good reasons not to push every commit public.
Yeah, every dev does that to a degree of one ticket, which shouldn’t take more that 2 days on average. So no, hiding code for half a year isn’t ok. I don’t know why you try to normalize it.
I’m not, it is normal, even in OSS development. Pushing every ticket is fine, but so is holding back until the work is done or until release. It is, and always has been, up to the project on when and how code goes public.
Its not their software until its released. They aren’t users until its actually released and actually deployed to a phone.
Development being private until release is NORMAL. I do it, every developer does it. All the changes live on my box until I’m ready for the world to see them.
I think that’s true, but it’s a different moral imperative than either open source (understood as just being able to get the code for the software you have) or Free Software (which was conceived when software came on tapes in the mail and completely fails to address project governance in the era of forges).
Cutting a release (and publishing) does cost significant time and effort. You effectively need to code-freeze, get all code merged into main, run all tests and QA, fix any breaking bugs, compete signoffs etc. On some of our small projects, doing a release could burn up to 2 weeks of real time, which on a monthly release cycle was killing us.
So I can almost buy their reasoning. But otherwise, agree that they can’t be trusted, and releasing once a quarter doesnt seem that hard.
They are still doing that work for select OEMs, just not pushing it to the public server.
Do you have a source for that? I can believe that select OEMs are getting preview internal access, but I strongly doubt they are releasing with ROMs cooked from those internal branches. That would open the OEMs to GPL requests/violations. And internal access doesnt mean doing the release processes that chew up time.
Giving preferential treatment to certain OEMs is its own issue though, but its a anti-competitive behaviour issue rather than a licencing issue.
I was overly vague, and “Android” means different things in different places. I usually say “AOSP” for Open Source Android and “Google Android” for open core Android. This also isn’t quite accurate.
AOSP is basically a repo, not a ROM, not an OS, not even code (technicaly). This has always been pushed to on “release”, not during development.
Google has it’s own (private) repos for development. I suspect some OEMs have access to HEAD.
Google used to publish device code for Nexus/Pixel devices. This stopped in 2025. This was separate to AOSP, but would build with AOSP for “Android Android” or “Open Source Android”. Some people would “add gapps” to get closer to “Google Android”.
Kernal code from Google for Pixel devices is still publically available as is required by the GPL. Basically no other part of Android is GPL and has this requirement.
A “release” pushed to AOSP used to basically line up with a Nexus/Pixel update. At the end of 2025 they changed it to 4 times a year, now they are changing it to twice a year.
“Android Security Bulletin” is a different thing, OEMs get early access to it. Everyone else gets delayed releases by about a quarter. This delay was new in 2025, this will continue to happen.
Google isn’t giving built ROMs to OEMs, even if it was, assuming it’s internal only, it wouldn’t be a GPL violation. AOSP has never distributed built ROMs.
You could just have less releases but still develop everything openly…
Of course. Although I can kinda see why they dont want to do that either. All the fly-by-night OEMs would be using dev and shipping half-baked ROMs (which I guess they do anyway, but it would be worse).
So just push everything to open source then, not only releases but branches? Nobody forces you to have fast release schedule, but you either open source or you are not. Releasing sources 2 times a year is not an open source.
Actually, it is open source. There is nothing wrong with developing in private and pushing public when its done. Every developer works that way to some degree or another. And there are good reasons not to push every commit public.
Yeah, every dev does that to a degree of one ticket, which shouldn’t take more that 2 days on average. So no, hiding code for half a year isn’t ok. I don’t know why you try to normalize it.
I’m not, it is normal, even in OSS development. Pushing every ticket is fine, but so is holding back until the work is done or until release. It is, and always has been, up to the project on when and how code goes public.
No there aren’t. All users (interested) need to know what their software is doing and be able to contribute to it.
Its not their software until its released. They aren’t users until its actually released and actually deployed to a phone.
Development being private until release is NORMAL. I do it, every developer does it. All the changes live on my box until I’m ready for the world to see them.
I think that’s true, but it’s a different moral imperative than either open source (understood as just being able to get the code for the software you have) or Free Software (which was conceived when software came on tapes in the mail and completely fails to address project governance in the era of forges).