• red_tomato@lemmy.world
    link
    fedilink
    arrow-up
    69
    ·
    edit-2
    10 hours ago

    Another movie pitch:

    Due to management decision, a code freeze has been mandated to the main branch. 50 feature branches have accumulated waiting to be merged.

    Management has now finally approved to lift the code freeze - but only for 24 hours. Will the poor engineering team manage to merge all feature branches in time?

    • Jesus_666@lemmy.world
      link
      fedilink
      arrow-up
      27
      ·
      edit-2
      6 hours ago

      Here’s one for a TV show.

      In 2022, a crack quality assurance team was made redundant by a CTO for a botched product launch they didn’t commit.

      These men promptly escaped from a maximally unstable job market to the LinkedIn underground.

      Today, still wanted by recruiters, they survive as soldiers of fortune.

      If you have a broken codebase, if no one else can help, and if you can find them, maybe you can hire the QA-team.

    • ugo@feddit.it
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      edit-2
      7 hours ago

      Very easy: merge everything, fix after the feature freeze. It’s a feature freeze, not a bugfix freeze.

      Edit: wait you said code freeze, my bad. Still, merge everything. If stuff doesn’t work after the freeze, management will unfreeze for fixes. Or they freeze a non-working product. Do stupid management, get stupid results. Not on me to make idiotic processes work.

    • grue@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      8 hours ago

      Merging all the feature branches in time is easy.

      Having the project compile afterwards is hard.

    • Otter@lemmy.ca
      link
      fedilink
      arrow-up
      16
      ·
      9 hours ago

      Is there a robust test suite?

      Merge, test, merge, test, patch, merge, test