[Development] Branching 5.0

Thiago Macieira thiago.macieira at intel.com
Mon Dec 3 22:40:24 CET 2012

On segunda-feira, 3 de dezembro de 2012 22.26.19, João Abecasis wrote:
> > Let's try to just push fixes for things that will block the release
> > <https://bugreports.qt-project.org/browse/QTBUG-27426>,
> Isn't this the definition of the "release" branch? If we are in
> release mode, if we only want fixes for blockers why not say that
> "master" IS the release branch for the time being?
> Saying that we'll open the "release" branch once the code is ready for
> RC but applying the rules of the "release" branch looks confusing at
> best.

That's partially true.

In the release branch, only the release team should be approving changes, 
which is different from what Sergio asked.

However, given how late we are with 5.0, it's better to be conservative now on 
the fixes and apply only those that are strictly necessary for the release.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121203/f05c95f2/attachment.sig>

More information about the Development mailing list