[Releasing] Current beta installers

Iikka Eklund iikka.eklund at digia.com
Mon Jul 30 13:00:55 CEST 2012

Back at office now so I can continue fixing the beta installer issues.
Is there any kind of priority list for the open items where to start?
There are plenty of issues mentioned in emails and in Jira but which
are the most important ones to start with?

What is the status of webkit?
What about the content for the 3rd party software licensing info dialog?

One other thing I noticed was that Jenkins produces Linux installers for 
each Ubuntu
distribution (10.x, 11.x, 12.x) but we currently build qt5 only against 
11.10 (32 and 64).
Is it decided that we need installer for each Ubuntu version?

- iikka

On 07/25/2012 12:33 PM, casper.vandonderen at nokia.com wrote:
> I obviously mean: It would be nice if you could let us know if you still
> notice big gaps
> Casper
> On 7/25/12 10:15 AM, "Vandonderen Casper (Nokia-MP/Oslo)"
> <casper.vandonderen at nokia.com>  wrote:
>> On 7/17/12 9:52 AM, "Vandonderen Casper (Nokia-MP/Oslo)"
>> <casper.vandonderen at nokia.com>  wrote:
>>> ________________________________________
>>> From: Mcdonald Jason (Nokia-MP/Brisbane)
>>> Sent: Tuesday, July 17, 2012 9:19 AM
>>> To: Vandonderen Casper (Nokia-MP/Oslo); Bornemann Joerg (Nokia-MP/Berlin)
>>> Cc: releasing at qt-project.org
>>> Subject: RE: [Releasing] Current beta installers
>>>>> A more severe issue: the docs are almost completely missing from
>>>>> assistant. Only the assistant docs are there.
>>>> That is because we don't have qhelpgenerator available in the script
>>>> that produces the installers, we just run "make>online_docs" in qtdoc
>>>> and copy that over (I think).
>>>> We should probably start running "make qch_docs" in qtdoc instead, which
>>>> requires qhelpgenerator from qttools.
>>>> The mksrc.sh script in qtrepotools/release-tools does that, but Digia
>>>> aren't using that script for their packages right now.  Consequently,
>>>> QtProject-generated source packages have docs, but Digia-generated
>>>> packages do not.  That will hopefully get resolved soon.
>>>> Note however that the docs in the QtProject-generated packages are
>>>> missing hyperlinks to most of the QML docs.  The snapshot online docs
>>> >from the doc team don't have as many missing links, so I'm guessing that
>>>> there's either still something missing from the black magic in mksrc.sh
>>>> or that its an offline versus online docs problem.
>>> Hmm, there seems to be a difference somewhere, I'm getting 220 extra qdoc
>>> errors when running "qch_docs".
>>> Also the command for qhelpgenerator does not work by default (probably we
>>> should use something different than "$${Qt.help.bins} to find
>>> qhelpgenerator).
>>> I will investigate.
>> Most(/all) of the problems with the QCH docs should be resolved now. It
>> would be nice if you still notice big gaps after Qt5 integration happens
>> and the packages are generated again.
>> Casper
> _______________________________________________
> Releasing mailing list
> Releasing at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/releasing

Mr. Iikka Eklund
Senior software engineer

Elektronikkatie 10
FI-90590 Oulu
Email: iikka.eklund at digia.com

Visit us at: www.digia.com or qt.digia.com
This message and any attachments are intended only for use by the named
addressee and may contain privileged and/or confidential information. If
you are not the named addressee you should not disseminate, copy or take
any action in reliance on it. If you have received this message in
error, please contact the sender immediately and delete the message and
any attachments accompanying it. Digia Plc does not accept liability for
any corruption, interception, amendment, tampering or viruses occurring
to this message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20120730/70e54a2e/attachment.html>

More information about the Releasing mailing list