[Development] Proposal: removing the release branches after the release

Knoll Lars Lars.Knoll at digia.com
Tue May 27 08:25:37 CEST 2014

On 26/05/14 21:59, "Thiago Macieira" <thiago.macieira at intel.com> wrote:

>I've just seen that all the Qt repositories got a 5.3.0 branch (including
>those for which a release not called "5.3.0" was produced).
>I'm proposing to reverse that. There's no point in having those branches,
>since after the code is tagged and released. There will never be any
>change to 
>the code under that same version number.
>If there's any need to make an emergency release on top of a given tag,
>release will get a new version number (without dashes, please) and we can
>create a branch with the appropriate name to make the release. And once
>is done, we remove the branch again.

I don’t see any problems with having named branches for patch level
releases, and it is what we agreed to some months ago. Can you explain why
you’d want to remove the branches once the release is done?


>This starts by removing all the 5.3.0 branches that have  just been
>Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
>Development mailing list
>Development at qt-project.org

More information about the Development mailing list