Hi!

I think the reason for this is that v6.7.0 is the API which is reviewed last 
time. Using it as a base ensures that API changes in 6.7.x release will be 
reviewed as well

br,
Jani

> -----Original Message-----
> From: Volker Hilsheimer <volker.hilshei...@qt.io>
> Sent: perjantai 7. kesäkuuta 2024 17.13
> To: Jani Heikkinen <jani.heikki...@qt.io>
> Cc: development@qt-project.org
> Subject: Re: [Development] HEADS-UP: Qt 6.8 API change review
> 
> >
> > On 4 Jun 2024, at 09:29, Jani Heikkinen via Development <development@qt-
> project.org> wrote:
> >
> > Hi!
> >  Qt 6.8 API Change Review is started, see
> https://bugreports.qt.io/browse/QTBUG-125859
> > generated diffs are here:
> >     • https://codereview.qt-project.org/q/topic:api-change-review-6.8
> >     • https://codereview.qt-project.org/q/topic:qml_api_review_6.8
> >  Please review the diffs as soon as possible.
> >  br,
> > Jani
> 
> 
> Is there a good reason for comparing 6.7.0 to 6.8, rather than 6.7 to 6.8? I 
> see a
> few differences that shouldn’t be there (or should be … different), because 
> the
> respective patch have also been cherry-picked to 6.7. E.g. qtmultimedia fixes 
> to
> the BiC bug.
> 
> 
> Volker
> 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to