• Emily (she/her)@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    23
    ·
    9 days ago

    It’s important to note that this is them moving in-development branches/features “behind closed doors”, not making Android closed source. Whenever a feature is ready they then merge it publicly. I know this community tends to be filled with purists, many of whom are well informed and reasoned, but I’m actually totally fine with this change. This kind of structure isn’t crazy uncommon, and I imagine it’s mainly an effort to stop tech journalists analysing random in-progress features for an article. Personally, I wouldn’t want to develop code with that kind of pressure.

    • thann@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 days ago

      Why would you want people to test your software on all sorts of random hardware when you could just pay people to test it on a smaller scale!

      • BeardedGingerWonder@feddit.uk
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 days 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?

        • boonhet@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 days 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

        • Victor@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          8 days 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.