[Development] Qt Purchasing in Qt 5.6

Eskil Abrahamsen Blomfeldt eskil.abrahamsen-blomfeldt at theqtcompany.com
Wed Aug 5 12:32:04 CEST 2015

On 08/05/2015 01:08 PM, Marc Mutz wrote:
> On Wednesday 05 August 2015 09:59:52 Oswald Buddenhagen wrote:
>>> How do we handle reviews beyond that? Should I make a patch to qt5.git
>>> and collect comments there, or would it be better if I make a mock
>>> change that includes the entire code base so that we can get inline
>>> comments? I'm not sure how this has usually been done before.
>> don't make it too meta.
>> what exactly you want people to review at which granularity level?
> If you already have exsiting customers, what guarantees have you given them re
> BC and SC? IoW: are we supposed to review API as well as implementation?

I really hope we can keep source compatibility and use deprecation, etc. 
if there is a need for changes to the API. Otherwise it will likely mean 
increasing the version number of the public version and 
maintaining/supporting two separate ones for us, which of course will 
eat into the time we have for other stuff.

Binary compatibility should not really be an issue on Android or iOS, 
since the libraries are always bundled in the former case and statically 
linked in the latter. Someone correct me if I'm wrong :)

-- Eskil

More information about the Development mailing list