My team has this one shared component that gets involved in like every feature’s development. This year, we’re loading like 5 different features onto it, all with different timelines, and my head’s about to explode trying to figure out how to make it all fly.

How does everyone else do their software releases? Do you freeze prod and then do one big release later? Throw everything into prod during dev, hope no one sees the unreleased stuff, and just announce it later? Or something else entirely?

  • Kbin_space_program@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    4 months ago

    If you have multiple branches you’re mixing into one:

    1. Have a code repo. Shockingly a consulting firm I worked at didn’t have a repo system.

    2. QA each branch.
      Merge all the code.
      Deploy to a testing server and QA that. Fix as needed
      Deploy to staging for final testing. Test and verify deployment procedure. Fix as needed
      Deploy to prod.