[Releasing] Qt 5.0 alpha released
simo.falt at nokia.com
simo.falt at nokia.com
Wed Apr 4 12:21:17 CEST 2012
I can't provide you an easy way but I can show you a way to get the alpha
out of git (see below). But yes, it is true that there isn't any tag in
git but I hope we will fix that in future releases. There was quite a lot
of last minute hassle while creating that, so it ended up to be this way.
But hey, it was first release from qt5 and now we see that all of our
processes are not quite there yet. This is the channel to start specifying
the releasing process for the next release.
But the git stuff:
>From qt5.git checkout 8e5b652334c76c9275d39b460fffad19a2150721
git submodule update
>From qtbase checkout master branch
>From qtwayland checkout 0.85 branch
>From qtwebkit qt-5.0.0-alpha-hotfix branch
The used sha1's from repo's above are inside release package in .sha1s
Then on top of this cherry pick following patches from gerrit:
The if you wan't to get exact copy of the zip and tar.gz file, take the
mksrc.sh script from qtrepotools/release_tools/ dir and use that to patch
the %QTVERSION% etc. Defines. The run it like this:
-i qlalr \
-i qtconnectivity \
-i qtjsondb \
-i qtdocgallery \
-i qtfeedback \
-i qtphonon \
-i qtpim \
-i qtqa \
-i qttranslations \
-i qtactiveqt \
$MKSRC -u $REPO_DIR -v $VERSION $IGNORES
On 4/4/12 11:21 AM, "ext Mika Boström" <mika.bostrom at nomovok.com> wrote:
>Let's try again - the first one was sent from wrong address.
>Thunderbird, multiple accounts, b0rked default accounts for filtered
>emails... (List admins can drop the earlier copy from review queue.)
>On 04/03/12 18:01, marius.storm-olsen at nokia.com wrote:
>> We are happy to announce the *Qt 5.0 alpha release*. This is the first
>> major Qt release since the Qt Project went live, and a large amount of
>> work and features have gone into this release.
>[Kept development@ as cc, may be of interest to them.]
>This is good news.
>I have a minor gripe, though. None of the resources I looked at (blog,
>wiki, git repos) contained the actual list of git commits used for the
>submodules in this release.
>qt5.git submodules show where the current "known-good" development
>snapshot points. There are no tags or releasing branches in the modules.
>As far as I can see, there is no easy way to reproduce the contents of
>the alpha release from qt5.git submodules. Even the build-from-git page
>(http://qt-project.org/wiki/Building_Qt_5_from_Git) simply states that
>master branches follow the ongoing development and submodules are
>updated to match the latest working combination. At the moment I don't
>know how to get a (pre-)release exported from git directly.
>I personally care for that because I've done some work of my own to get
>Qt5 built nicely from individual modules. I've been at it since last
>summer, to be honest. The current results may be viewed at
>That is the result of handcrafted specs and some trivial patching. I
>would love to have the modular build match the releases and steps
>leading up to Qt5 final. We could have a day 1 packaged release, and you
>could have a testing ground for modular builds.
>A straightforward way to reproduce releases from qt5.git would be a
> Mika Boström / mika.bostrom at nomovok.com
> Software Architect
>Releasing mailing list
>Releasing at qt-project.org
More information about the Releasing