[Development] Feature freeze and Alpha

lars.knoll at nokia.com lars.knoll at nokia.com
Sun Feb 5 18:06:41 CET 2012

On 2/5/12 4:27 PM, "ext Robin Burchell" <robin+qt at viroteck.net> wrote:

>On Sun, Feb 5, 2012 at 3:12 PM,  <lars.knoll at nokia.com> wrote:
>> * finish codecForCStrings & codecForTr removal (QTBUG-21872)
>Relatedly - but I think it probably deserves separate mention - would
>be the defaulting of passing raw bytes to QString to use utf8
>encoding. It's a little more involved, but definitely something that
>should be 5.0 material. I have a raw patch tackling a lot of this done
>locally, I just need to finish massaging QStringBuilder to do my
>bidding, polish it up, and push for initial review. I hope to find
>time for this done during this week.

Ok, that was included in the task for me.

>> * Joao's container work (QTBUG-23589)
>Another related item from me, which perhaps I should open a bug
>for(?): the deprecation of qMalloc/qRealloc/qFree. Most of this has
>actually been done, except for inline uses. I've been holding back on
>tackling that further until the containers branch is merged so I have
>a clearer picture of what is left to actually fix. I suppose this
>isn't considered a 5.0 blocker unless we want to actually remove those
>methods rather than just deprecate them though.

No, this is a rather simply change that we should just get done before 5.0
final is out. We can't remove the methods anyway, so it's purely about not
using them anymore and marking them as QT_DEPRECATED_SINCE(5, 0).


More information about the Development mailing list