[Development] Qt 4.6.5 and 4.7.6 release candidates available

[Giuseppe D'Angelo]

On 21 February 2013 12:53, Turunen Tuukka <Tuukka.Turunen at digia.com> wrote:
>
>
> This is incorrect assumption as we have discussed this before making the
> RC1 - it just took a lot of time due to other release creation activities
> to continue the releasing work, so it seems that some persons (at least
> Thiago) just noticed it now when we are making RC2.

The problem is that you never announced the SHA1 of the commits of the
RC releases, and thus nobody immediately figured out that you were
going to release from the digia branches, not the official ones. (You
didn't even push the tags on the repository -- there are no v4.7.6-rc*
or v4.6.5-rc* around.)

What I do see instead that you *already pushed* the v4.7.6 and v4.6.5
tags without telling anyone, and those tags were created *more than
one week* before the first message of this thread (in which you
announced that you wanted to create release candidates):

> $ git show v4.7.6
> tag v4.7.6
> Tagger: Marko Valtanen <marko.valtanen at digia.com>
> Date:   Wed Dec 12 17:04:36 2012 +0200
>
> Qt 4.7.6 opensource release
>
> commit 41d648720d9bd87381b85ade3da0d91456ff31e0 (tag: refs/tags/v4.7.6)
>
> $ git show v4.6.5
> tag v4.6.5
> Tagger: Marko Valtanen <marko.valtanen at digia.com>
> Date:   Wed Dec 12 12:27:38 2012 +0200
>
> Qt 4.6.5 opensource release
>
> commit 63eb2e6a39c1a5bee6551cd6a7749a85856d5393 (tag: refs/tags/v4.6.5, refs/remotes/origin/4.6-digia)

I don't have access to the reflog, but according to gitorious, they
have been pushed the same day at 15:04 / 15:07 CET. Also, v4.7.6 seems
to point at the wrong commit, as it's a commit outside any branch:

> $ git log --graph --oneline --decorate origin/4.7-digia v4.7.6
> * 41d6487 (tag: v4.7.6) Changes-4.7.6 file updated
> * 436cf69 Fix binary incompatibility between openssl versions
> | * 090ca16 (origin/4.7-digia) Changes-4.7.6 file updated
> | * 7ce4690 Fix binary incompatibility between openssl versions
> |/
> * b67ee40 updated LICENSE.PREVIEW.COMMERCIAL
> * cba3ada Nokia to Digia for LGPL-exception file

So at the very least (no matter what we decide to do with the version
numbering) that tag needs to be deleted and recreated. man git-tag at
"On Re-tagging" offers a nice email template you could use for the
purpose.

Cheers,
-- 
Giuseppe D'Angelo