On Mon, 6 Aug 2012 22:13:30 ext joao.abeca...@nokia.com wrote:
> Fire-hose is a development branch, things may be variously broken at all
> times. Typically, developers in this mailing list will be tracking that
> branch.
>
> Leaky-faucet is deemed beta quality and somewhat more stable. At the ver
On terça-feira, 7 de agosto de 2012 01.00.54, Olivier Goffart wrote:
> ---+--+-- fire-hose
>/ \ / / / / / / / / \ / / / / / /
> --+ +-+++ +-++ leaky-faucet
> / \ / / / \ / / / \ / / / \ / /
On Monday 06 August 2012 21:22:27 joao.abeca...@nokia.com wrote:
[...]
>
> -+--+-- fire-hose
>\ \
> -+-+--+++-+--++ leaky-faucet
>\\\\\\
> -+-
On terça-feira, 7 de agosto de 2012 00.20.56, Thiago Macieira wrote:
> On segunda-feira, 6 de agosto de 2012 22.13.30, joao.abeca...@nokia.com
wrote:
> > Leaky-faucet is deemed beta quality and somewhat more stable. At the very
> > least it shouldn't break as often. We can expect that more people w
On segunda-feira, 6 de agosto de 2012 22.13.30, joao.abeca...@nokia.com wrote:
> Leaky-faucet is deemed beta quality and somewhat more stable. At the very
> least it shouldn't break as often. We can expect that more people will be
> willing to track this branch with their own development.
One more
Thiago Macieira wrote:
> One think I'd like to know from others is: what does dripping-bucket contain
> when changes are not going in, in-between releases? From the description and
> from the graph, it sounds like that branch contains the next release before
> it is tested out. That is, it's a bran
Thiago Macieira wrote:
> Thanks for putting it together. I like it. It's what we had discussed over a
> year ago and it makes sense to me.
For context, I proposed this setup internally before. The beginning of Qt 5's
development made most of the proposal temporarily mute.
It is now a good time to
On segunda-feira, 6 de agosto de 2012 21.22.27, joao.abeca...@nokia.com wrote:
> What do others think?
Thanks for putting it together. I like it. It's what we had discussed over a
year ago and it makes sense to me.
I think that the patch release process could be adjusted a little. For
example, th
Hello Qt-ians,
While releasing Qt 5.0.0 is an ongoing process, I think this is a good
time to start planning future releases (5.0.1, 5.1.0, etc.) and, most
importantly, we need to discuss *how* we'll get them out on time.
With the setup we now have we should quickly move to a strict time-based
re
What do these two variables mean?
I saw QT_PRIVATE before and now I see QT_FOR_PRIVATE in .pro files from qtjsondb
(client.pro, for example).
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi all,
I've done a query of all contributions older than 6 months, which have not yet
been merged. It would be great if you could have a look to see which ones are
obsolete and can be abandoned, and which ones are targeted the 5.1 release.
If you have a WIP which is intented for 5.1, please st
> Message: 2
> Date: Mon, 6 Aug 2012 14:57:38 +0800
> From: Fred Fung
> Subject: Re: [Development] [Qt 4.8 with directfb]Web image rendering
> problem
> To: development@qt-project.org
> Message-ID:
> <
> calv-t3351o6fp6mzbqvp44qhxwr6lqqowvh+j2c5t5aqpnu...@mail.gmail.com>
> Content-
On Friday, August 03, 2012 13:10:43 Salovaara Akseli wrote:
> There are a few contributions pending to be merged to 4.8 in Gerrit (link:
> http://codereview.qt-project.org/#q,project:qt/qt+status:open,n,z). It
> would be great if all maintainers who have not yet done so go through
> these for thei
On 08/06/2012 12:52 PM, lars.kn...@nokia.com wrote:
> We already have QT_BEGIN/END_NAMESPACE macros used throughout, as well as a
> module specific qmoduleglobale.h. So I would think it should be possible to
> do the change in a rather straightforward way.
>
> I can't see how this could destabili
On 06/08/2012 03:47, ext lars.kn...@nokia.com wrote:
...
> The first one is the fact that we have a few modules in there that
> are basically unmaintained for a year and not really functional
> anywhere. The document gallery is such an example and is the first
> one I would like to remove (see
> ht
On Aug 6, 2012, at 11:33 AM, ext Thiago Macieira
wrote:
> On segunda-feira, 6 de agosto de 2012 16.31.40, Aaron McCarthy wrote:
>> As an add-on should Qt Location be moved out of the global namespace and
>> into its own like other Qt add-ons? I know former Qt4 modules are exempt
>> from this r
On segunda-feira, 6 de agosto de 2012 16.31.40, Aaron McCarthy wrote:
> As an add-on should Qt Location be moved out of the global namespace and
> into its own like other Qt add-ons? I know former Qt4 modules are exempt
> from this rule, but what about former Qt Mobility modules or former Qt 5
>
Hi,
I'm currently going through qt5.git, looking at all the modules. I would like
to see whether all modules currently in there should be or need to be part of
this set. Currently I can see two problems there.
The first one is the fact that we have a few modules in there that are
basically un
On Friday 03 August 2012 15:42:49 marius.storm-ol...@nokia.com wrote:
> On 03/08/2012 07:49, ext Thiago Macieira wrote:
> > And operator== can't change incompatibly.
>
> Does this mean that we should have an
> bool QDateTime::isIdentical(const QDateTime &dt)
> function too (effectively an ope
Hi Aaron,
On Aug 6, 2012, at 8:31 AM, ext Aaron McCarthy wrote:
>> as one of the first consequences of the situation in Brisbane, I'd like to
>> do some changes to our list of essential modules. You can see the current
>> list at http://qt-project.org/wiki/Qt-Essentials-Modules .
>>
>> I intend
20 matches
Mail list logo
