[Development] QtWebKit is coming back (part 2)

Sergio Martins sergio.martins at kdab.com
Thu May 4 16:20:55 CEST 2017

On 2017-05-04 14:51, Konstantin Tokarev wrote:
> 03.05.2017, 17:27, "Sergio Martins" <sergio.martins at kdab.com>:
>> On 2017-05-03 15:02, Konstantin Tokarev wrote:
>>>  Remaining question is versioning. While it's fine to dub current
>>>  release "5.9" (but not 5.0, because we will have another WebKit 
>>> update
>>>  in 5.10 time frame), using Qt versions in QtWebKit has downsides:
>>>  1. It is not clear if 5.N+1 ships with the same WebKit branch as 
>>> 5.N,
>>>  or is updated
>>>  2. It makes people believe that QtWebKit 5.N should be used with Qt
>>>  5.N only. QtWebKit supports wide range of Qt versions (starting from
>>>  5.2 as of now), and can be used e.g. as security update in Linux
>>>  distro that does not normally update Qt version during its life 
>>> cycle.
>>>  Any comments?
>> If Qt and QtWebKit will have different release schedules then that
>> numbering would indeed confuse people.
> What about choice of new versioning scheme?
> I'm leaning towards "6.0.0" number, because it's larger than any 5.x
> and makes it
> clear that versioning is different now. Bug fixes will increment patch
> version (6.0.x),
> WebKit updates minor version (6.1.x etc), API/ABI breaking changes - 
> major
> verison (7.0 etc.)

If you go down that route just make sure 7.0 is out before Qt 6 is 
released, otherwise it's confusing too.

No idea about your other questions.

Sérgio Martins | sergio.martins at kdab.com | Senior Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - The Qt, C++ and OpenGL Experts

More information about the Development mailing list