branches contra tags for releases.

[Jan Iversen]

Hi

Is there a reason why we use tags instead of branches for a release. I am used to having a release branch for 2 reasons:
- work on master is not blocked but continues normally (with cherry pick to the release branch)
- it is easy to make a release patch if needed.

so hence my question.
rgds
jan I

Enviado desde mi iPad

[Lubomir I. Ivanov]

Post by Jan Iversen
Hi
- work on master is not blocked but continues normally (with cherry pick to the release branch)
- it is easy to make a release patch if needed.

i don't mind our current workflow.
makes the life of the maintainers easier.

also our code/docs/string freeze period is very short.

lubomir
--

[Dirk Hohndel]

Post by Jan Iversen
Hi
- work on master is not blocked but continues normally (with cherry pick to the release branch)
- it is easy to make a release patch if needed.

There are different philosophies on how to manage a git repo. We tried
release branches and it was generally not worth the hassle. We typically
slow down master for just a few days (because we have no serious release
process, let's be honest about it), so the inconvenience for the
developers really isn't that big. And it removes the issue of ending up
with patches going to multiple branches. We don't have the scale and the
resources to really deal with providing updates to older releases, anyway.

When we did the Gtk->Qt transition this made sense. We've done it in other
circumstances where massive changes made master a bit unstable (or lost us
features) and therefore it was reasonable to have a stable branch off of a
release. But in general... I don't see a ton of value.

/D