<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto">Yep, the current version of the application in 5.27 will launch the welcome experience and store it in config properly, the only thing needed to ensure it'll work for the update page come next release is the LastSeenVersion key. I've prepared
a minimal merge request for the 5.27 branch:</div>
<div dir="auto"><br>
</div>
<div dir="auto"><a rel="noreferrer noopener" href="https://invent.kde.org/plasma/plasma-welcome/-/merge_requests/51">https://invent.kde.org/plasma/plasma-welcome/-/merge_requests/51</a> </div>
<div dir="auto"><br>
</div>
<div dir="auto">Oliver</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Nate Graham <nate@kde.org><br>
<b>Sent:</b> Tuesday, January 24, 2023 8:03:36 PM<br>
<b>To:</b> plasma-devel@kde.org <plasma-devel@kde.org>; David Edmundson <david@davidedmundson.co.uk><br>
<b>Cc:</b> olib141@outlook.com <olib141@outlook.com><br>
<b>Subject:</b> Re: Plasma 5.27 feature freeze exception request</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">We could do that I think, right Oliver?<br>
<br>
Nate<br>
<br>
<br>
<br>
On 1/24/23 12:59, David Edmundson wrote:<br>
> I'm not very happy accepting that MR. It's not that minimal.<br>
> <br>
>> so that we have adequate metadata set for the following Plasma<br>
> version.<br>
> <br>
> Can we backport just:<br>
> ```configGeneral.writeEntry("LastSeenVersion", "5.27");```<br>
> <br>
> ?<br>
> <br>
> The rest is not needed on the first release from my understanding?<br>
</div>
</span></font></div>
</body>
</html>