[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: kio-extras and the KF5/KF6 period
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-06-21 10:31:47
Message-ID: CA+XidOH71bbwT5ZXfaR7qG3ObqcfjaaY27LcrmzfY8v=UZ6pxg () mail ! gmail ! com
[Download RAW message or body]

On Wed, Jun 21, 2023 at 8:22 PM Harald Sitter <sitter@kde.org> wrote:

> On Tue, Jun 20, 2023 at 11:23 PM Sune Vuorela <nospam@vuorela.dk> wrote:
> >
> > On 2023-06-20, David Redondo <kde@david-redondo.de> wrote:
> > > Harald and I prototyped another solution to build a Qt
> > >  5 and Qt 6 version out of the same repo and employed it on
> > > plasma-integration:
> https://invent.kde.org/plasma/plasma-integration/-/
> > > merge_requests/91
> >
> > Did I miss something or is this just branching but without having git to
> > help us move stuff between versions?
>
> Yes but no. If we have two branches we also need two tars and everyone
> needs to do two things. If we have everything in the same branch then
> everything is as usual. Also, the sources are so divergent that
> picking is bound to be annoying.
>

It sounds like we are approaching (or have already hit) a "crossroads"
where it is time for the Qt 5 codebase to enter a stable release only
phase, with master becoming Qt 6 exclusive.
Splitting the code into separate Qt 5 / Qt 6 folders sounds like it will be
difficult to ensure that all bug fixes are applied equally to both sides.


>
> HS
>

Cheers,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Wed, Jun 21, 2023 at 8:22 PM Harald Sitter &lt;<a \
href="mailto:sitter@kde.org">sitter@kde.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Jun 20, 2023 \
at 11:23 PM Sune Vuorela &lt;<a href="mailto:nospam@vuorela.dk" \
target="_blank">nospam@vuorela.dk</a>&gt; wrote:<br> &gt;<br>
&gt; On 2023-06-20, David Redondo &lt;<a href="mailto:kde@david-redondo.de" \
target="_blank">kde@david-redondo.de</a>&gt; wrote:<br> &gt; &gt; Harald and I \
prototyped another solution to build a Qt<br> &gt; &gt;   5 and Qt 6 version out of \
the same repo and employed it on<br> &gt; &gt; plasma-integration: <a \
href="https://invent.kde.org/plasma/plasma-integration/-/" rel="noreferrer" \
target="_blank">https://invent.kde.org/plasma/plasma-integration/-/</a><br> &gt; &gt; \
merge_requests/91<br> &gt;<br>
&gt; Did I miss something or is this just branching but without having git to<br>
&gt; help us move stuff between versions?<br>
<br>
Yes but no. If we have two branches we also need two tars and everyone<br>
needs to do two things. If we have everything in the same branch then<br>
everything is as usual. Also, the sources are so divergent that<br>
picking is bound to be annoying.<br></blockquote><div><br></div><div>It sounds like \
we are approaching (or have already hit) a &quot;crossroads&quot; where it is time \
for the Qt 5 codebase to enter a stable release only phase, with master becoming Qt 6 \
exclusive.</div><div>Splitting the code into separate Qt 5 / Qt 6 folders sounds like \
it will be difficult to ensure that all bug fixes are applied equally to both \
sides.</div><div>  </div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
HS<br></blockquote><div><br></div><div>Cheers,</div><div>Ben  </div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]