Ahhh, I'm sorry, I misunderstood your email. Yes, you're right, in that case
the branch makes no difference and beta is a better name.
Simon
From: Development on
behalf of Thiago Macieira
Sent: Friday, December 23, 2016 4:42:12 PM
To: development@qt-project
Em sexta-feira, 23 de dezembro de 2016, às 13:27:30 BRST, Simon Hausmann
escreveu:
> I find that the branch is relevant in this context, as it relates to the
> amount of patches going in. The amount of patches going in is IMO related
> to the probably of introducing regressions. The process around
Hi,
I find that the branch is relevant in this context, as it relates to the amount
of patches going in. The amount of patches going in is IMO related to the
probably of introducing regressions. The process around the release branch, as
opposed to the "minor branch", as proven to be a useful me
Em sexta-feira, 23 de dezembro de 2016, às 07:17:01 BRST, Tuukka Turunen
escreveu:
> > Call it beta 2 (or gamma 1) right after branch and one we've iterated and
> > we could have released, we call it release candidate. We release them
> > more often, with more iterations, so that we get more feedb
>>> cd gui/ && ( test -e Makefile ||
>>> /Users/tim/dev/qt3rd/build-Qt-5.x-dev-macx-clang-static/qtbase/bin/qmake
>>> -o Makefile /Users/tim/dev/qt3rd/qtbase/src/gui/gui.pro -qtconf
>>> /Users/tim/dev/qt3rd/build-Qt-5.x-dev-macx-clang-static/qtbase/bin/qt.con
>>> f -- -qt-zlib -qt-harfbuzz -no-glib
