Comment on Google will move Android AOSP development behind closed doors

• pinball_wizard@lemmy.zip ⁨1⁩ ⁨month⁩ ago

  Would you really want everyone in the world looking at every end of day commit before you’ve refactored it into something vaguely passable?

  Honestly, it has been fine. Almost nobody really pays attention to anything they don’t care about, and most people who do care tend to be pretty helpful.

  source
• victorz@lemmy.world ⁨1⁩ ⁨month⁩ ago

  Heck, I’ll sometimes make a wip.diff file and scp it back and forth between work and home machines just because the code feels not ready for other eyes.

  source

  • pinball_wizard@lemmy.zip ⁨1⁩ ⁨month⁩ ago

    While I’m way too lazy to do that myself, I respect you for the skill and effort.

    source

    • victorz@lemmy.world ⁨1⁩ ⁨month⁩ ago

      😅 it’s not often nowadays, I’m not fresh meat at work anymore so I feel less insecure these days lol

      source
• boonhet@lemm.ee ⁨1⁩ ⁨month⁩ ago

  Who tf looks at feature branches unless it’s particularly relevant to them or they’re reviewing a PR?

  It’s not like they merge half-baked features straight to master every day lol

  source

  • BeardedGingerWonder@feddit.uk ⁨1⁩ ⁨month⁩ ago

    So what exactly are we losing?

    source

    • boonhet@lemm.ee ⁨1⁩ ⁨month⁩ ago

      You can’t review changes in the next build before it’s actually released?

      Currently you can still keep up with the master branch. PRs are merged a fair bit more often than new builds are made.

      source
• JackbyDev@programming.dev ⁨1⁩ ⁨month⁩ ago

  When that code is used on devices all over the world for many very important tasks, yes.

  source

  • BeardedGingerWonder@feddit.uk ⁨1⁩ ⁨month⁩ ago

    Why do you feel that Vs when merges happen?

    source