[Releasing] [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights
Thiago Macieira
thiago.macieira at intel.com
Thu Oct 4 14:59:04 CEST 2012
On quinta-feira, 4 de outubro de 2012 12.31.00, Turunen Tuukka wrote:
> Ok, back to the options.
>
> We can issue 4.8.3-1 now with the copyright change and MinGW fix, no other
> fixes in. These packages are ready and tested for both open-source and
> commercial licensees.
I don't like that. If it were just a packaging issue, I'd accept a re-release
of the same code. Since it isn't, since there is more than just packaging and
copyright headers, it should be called 4.8.4.
And it should include the SSL fix. That's more important than even the MinGW
fix.
Now, I'm not asking you to restart the whole release process and test
everything, which takes days and people who are busy with Qt 5. You said you
have the packages already. What we're asking is that:
1) apply the SSL fix
2) change the version number to 4.8.4
3) rebuild the packages
And in the repository, do the procedure that Stephen suggested. We won't
release out of the branch, but instead we'll create the tag based on the
contents of the release. It's backwards, but it works.
I can't do that and Stephen can't do that because we don't have the permission
to send merge commits to Gerrit. Only people in this group can:
https://codereview.qt-project.org/#admin,group,14
Ask one of them to do it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20121004/a3ee88ec/attachment.sig>
More information about the Releasing
mailing list