> I don’t see why a “stable” branch makes it easier for anyone than 5.x > branches. 5.x with highest x is what we > currently call stable branch. Maybe people who ‘casually’ commit/committed to > Qt Creator can say if it was hard > for them to find out which is the development branch, and which is the branch > of the current ‘stable’ Qt Creator > release series.
You can not follow them as we do now with stable branch. For example, I have a stable checkout that I can safely pull and it always points to the current stable version, not some old release, it means that I do not need to check if a new branch appeared and then switch to it. It is something really nice and useful. I really appreciate that I do not have to know Qt release number to push a doc fix or some trivial patch, but I may agree that it is not crucial. Cheers, Jędrek ________________________________________ Od: [email protected] [[email protected]] w imieniu Ziller Eike [[email protected]] Wysłano: 20 lutego 2014 12:50 Do: Thiago Macieira Cc: [email protected] Temat: Re: [Releasing] rethinking the branching scheme On Feb 19, 2014, at 9:05 PM, Thiago Macieira <[email protected]> wrote: > Em qua 19 fev 2014, às 16:35:05, Ziller Eike escreveu: >> We have to “remember" that sha. A natural way to do that is to have it as >> HEAD of a 5.2 branch > > We have that. It's the old/5.2 branch. aha, wasn’t aware of that (also because that doesn’t exist in qt5.git) Sorry, I think it’s a mess. It’s really hard to find out which branch now actually contains code for which version of Qt. I don’t see why a “stable” branch makes it easier for anyone than 5.x branches. 5.x with highest x is what we currently call stable branch. Maybe people who ‘casually’ commit/committed to Qt Creator can say if it was hard for them to find out which is the development branch, and which is the branch of the current ‘stable’ Qt Creator release series. dev is dev, that’s fine. release is basically release-management-private, fine too, except that I don’t see an advantage of a single release branch for all versions, over release-5.x.y branches (that might even get deleted after the release. we have tags for the final releases). All in all, to me it seems that the current dev/stable/release setup has multiple disadvantages, and I don’t see advantages of it. > Right now, it doesn't exist because the release branch contains[*] it, for the > moment. > > [*] no, it doesn't. For qtbase, it should be > d7b0581c1c2ef60c08d238dae39298af6904918f. > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Releasing mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/releasing -- Eike Ziller, Senior Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing _______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing
