230
Breaking: Google will now only release Android source code twice a year
(www.androidauthority.com)
this post was submitted on 06 Jan 2026
230 points (99.6% liked)
Android
20946 readers
154 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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).