On segunda-feira, 18 de março de 2013 14.36.41, Giuseppe D'Angelo wrote: > On 18 March 2013 14:22, Ahumada Sergio <[email protected]> wrote: > > About the tag, one could argue that making the tag (and alpha release) > > before or after the merge might be the same. > This is not only about making the 5.1.0-alpha1 tag. This is about not > breaking forward binary compatibility in stable unless extraordinary > circumstances. The branch guidelines imply that we should not merge > unless we are (almost) in beta quality, see > http://i.imgur.com/N1jVW.png (from > http://qt-project.org/wiki/Branch-Guidelines , 2nd picture).
That was not my intention when I wrote that. "dev" is already in alpha state. As soon as we do the feature-freeze, we can release the alpha and it should be fine. And Sergio is right: whether the tag appears shortly before or shortly after the dev/stable does not make a difference. > We can declare dev frozen and not accept any new > significant/destabilizing feature, but I disagree on the point that we > should retarget small new features (pending, not yet +2d) to stable, dev doesn't freeze. The freezing of Qt 5.1 *is* the merge of dev into stable. > as well as getting the first round of API feedback (which could mean > API/ABI breaks) in stable. (That of course could still happen after a > beta released from -stable, but it would probably require much > stronger arguments in order to go through.) -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing
