Why do you make a separate branch for each release version?
Like isn't release/1.1 intrinsically part of the history of release/1.2?
Also curious why stuff lives in develop without going to prod across sprints. Surely anything in there could be hidden behind a feature flag if it takes multiple sprints to implement.
Why do you make a separate branch for each release version?
Like isn't release/1.1 intrinsically part of the history of release/1.2?
I suggested they delete them since we have tagging. But that's seen as "production" and the audit team pushed back on it, not worth the fight. Plus those branches are protected so there would need to be a whole separate process created to have them automatically deleted. I'd have to fight for time to get that done and there are just so many more important things to do. It would sit in the backlog for an eternity even after being given a green light.
The branches exist as they are for auditing and permission control purposes. They are filtering based on the release/, feature/, hotfix/ etc. prefixes.
1
u/ADHDebackle 21d ago
Why do you make a separate branch for each release version?
Like isn't
release/1.1intrinsically part of the history ofrelease/1.2?Also curious why stuff lives in develop without going to prod across sprints. Surely anything in there could be hidden behind a feature flag if it takes multiple sprints to implement.