<table><tr><td style="">ltoscano added a comment.
</td></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/T10812#184411" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T10812#184411</a>, <a href="https://phabricator.kde.org/p/jriddell/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@jriddell</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Frameworks has its own release schedule and that works well. Plasma fits in with that not the other way round.</p>
<p>For version numbers I think we should do as I did in Plasma and define some cmake variables to get used then go through all the apps where nobody much cares and set them to use the kde applications version number. We can find out which apps have maintainers who want it to have their own version number and work out a sensible cmake syntax for that if it's useful.</p></div>
</blockquote>
<p>Which is exactly what already happens.</p></div></div><br /><div><strong>TASK DETAIL</strong><div><a href="https://phabricator.kde.org/T10812">https://phabricator.kde.org/T10812</a></div></div><br /><div><strong>To: </strong>ngraham, ltoscano<br /><strong>Cc: </strong>aspotashev, apol, jriddell, xyquadrat, jtamate, vkrause, lbeltrame, ltoscano, cfeck, aacid, Yakuake, Okular, Dolphin, Kate, Spectacle, Konsole, Gwenview, KDE PIM, KDE Games, KDE Applications, ngraham<br /></div>