Elektrine lite

← Feed

@red_tomato@lemmy.world

2026-04-12 11:08 UTC

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?

Replies (5)

  • @otter@lemmy.ca 2026-04-12 11:45

    Is there a robust test suite? Merge, test, merge, test, patch, merge, test

    Open ##1194424

  • @grue@lemmy.world 2026-04-12 13:02

    Merging all the feature branches in time is easy. Having the project compile afterwards is hard.

    Open ##1194430

  • @ugo@feddit.it 2026-04-12 14:01

    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.

    Open ##1194434

  • @Jesus_666@lemmy.world 2026-04-12 14:27

    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.

    Open ##1194436

  • Merge/test/fix on a separate branch and then merge this into main when the freeze lifts?

    Open ##1194438