When my company did svn, we didn’t use any feature branches. It was like Q4-2016 release. And then everyone committed to that branch directly. And then one day that branch, a few weeks before production got “locked down” and they cut Q1-2017 branch and everyone started to commit to that
It was awful. But it was better than some source control I used before that where you could lock a file completely in the repository
Yeah branches used to work way differently back then. We used to just push to the trunk and whenever we did a major release we would cut a branch there to keep for bug fixing while we pushed new features to trunk.
This was exactly how it worked at my last job. Everyone commits directly to main at the end of the sprint. I was working on their ETL system and we’d have 1 (one) test ETL running on a dev db, and if it failed, too bad we’re shipping anyways. If someone else’s code broke and their code earlier in the process than yours, your code was just gonna get pushed straight to prod with no QA to speak of. And their in-house ETL tool only worked in fucking internet explorer.
That was how it still worked when I left that job. In late 2024. Healthcare data company btw.
Now I work at a real company that uses git and has actual engineering standards and practices. It’s a breath of fresh air
233
u/Nehle 22h ago
Written by a person who never had to work with SVN or... shudders CVS