Trunk Based Development
trunkbaseddevelopment.com
A portal on this practice

I’ve heard it thrown around in professional circles and how everybody’s doing it wrong, so… who actually does use it?

For smaller teams

“scaled” trunk based development

    • MajorHavoc@programming.dev
      14·
      2 months ago

      Welcome time traveler. If you’re able to return to your own timeline, buy some Apple stock.

      /joking

      But I hope your team does migrate. SVN is pretty bad, compared to git.

    • CrypticCoffee@lemmy.ml
      3·
      2 months ago

      Do you really need to make a case? Does your company not trust devs? Is there people leading that have no idea about technology? SVN is dead. Many devs won’t touch it. It’s best way to say to new candidates your company is backwards. Many would refuse to work in a company that uses a version control system that has been dead 7 years.

      • KindaABigDyl@programming.dev
        2·
        2 months ago

        It’s effort to switch, and we don’t benefit from having separate copies of the repo bc we’re so small. No one steps on eachother’s toes, so distributed version control isn’t necessary.

        Now, the fact that most devs know git and SVN is dead is not lost on our CTO, but putting the effort to switch over doesn’t provide direct value to the customer, so I have to make the case that switching to git would do enough from a productivity and maintenance standard to effect customers.

        • shasta@lemm.ee
          11·
          2 months ago

          But just productivity and maintenance but if your devs start to leave or retire, you’re not gonna get the best quality replacements for them if you’re using outdated tech. No one wants to learn new skills that aren’t going to help with their career growth.