We have a deployed branch. It doesn’t get merged into master until it gets reviewed… the technical debt got too big so it never gets reviewed and we just keep branching off deployed
He drops commits but keeps on forgetting
What he wrote down, CI goes so loud
He tags the release but it won’t go out
E2es choking now, pipeline’ jokin’ now
Clock’s run out, time’s up, over, blaow.
Well, when you said “we have a deployed branch”, you could just have stopped there. All the rest is just what happens after you decide to rename your master branch.
Depends on the field you’re in. At my previous company to release a new system for internal use only I had to go through 19 validations(each one 50-100 pages of manual tests). None of it had real source control except uploading final zip of files(no source code, just the enable files).
I wrote all the files, wrote all the test cases, wrote all the documentation, executed everything and wrote most of the reports. They just fired me last week so hope they have fun when they need to update something…
We have a
deployedbranch. It doesn’t get merged intomasteruntil it gets reviewed… the technical debt got too big so it never gets reviewed and we just keep branching offdeployedYes, we’ve had first
masterbranch, but what about secondmasterbranch?Ah yes, by the end of the week we will have achieved full apotheosis:
master-final-v3-deployed-2025_08_01-usethisonejesus
He can’t help you. Y’all need Linus.
What’s he going to do? Drop commits? /s
He drops commits but keeps on forgetting
What he wrote down, CI goes so loud
He tags the release but it won’t go out
E2es choking now, pipeline’ jokin’ now
Clock’s run out, time’s up, over, blaow.
Well, when you said “we have a deployed branch”, you could just have stopped there. All the rest is just what happens after you decide to rename your master branch.
We build off develop and only update master once a year or so. Our company also pays 4 V&V engineers, compared to 9 software devs.
After a release cycle, we update master. Master has never, never been built by itself.
Depends on the field you’re in. At my previous company to release a new system for internal use only I had to go through 19 validations(each one 50-100 pages of manual tests). None of it had real source control except uploading final zip of files(no source code, just the enable files).
I wrote all the files, wrote all the test cases, wrote all the documentation, executed everything and wrote most of the reports. They just fired me last week so hope they have fun when they need to update something…
I’m a software engineer, and I don’t even know what a v&v engineer is.
Verification & validation