<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 3 July 2016 at 17:28, Camilla Boemann <span dir="ltr"><<a href="mailto:cbo@boemann.dk" target="_blank">cbo@boemann.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Sunday 03 July 2016 01:10:52 Jaroslaw Staniek wrote:<br>
> How to number components of Calligra 3? I mean apps and libs.<br>
<br>
</span>Well I wouldn't mind dates or codenames for the public versioning, but<br>
versions numbers are also for internal usage, so we know when we make big<br>
api/code changes<br>
<br>
And I see no reason why we should change our internal numbering to 4.x just<br>
because you make huge ui changes.<br></blockquote><div><br><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;display:inline">Yes, I see this as a point for </div> <div class="gmail_default" style="font-family:monospace,monospace;font-size:small;display:inline">not having the internal versioning synced between all Calligra components. In Kexi next up can go backward-incompatible changes in one app, and this development can happen in parallel to the maintenance of the "current stable". These are possible reasons to more frequent increasing of the major number for one app.<br>Any sharing between Kexi and other calligra apps would happen via separate repos anyway. Like kdiagram, kdb/kreport - that's most probably between Kexi and Plan. Once it's not a monolith anymore, all these bits have can change APIs to address different needs. (co-installability of many versions can be a way to keep compatibility I hope)<br></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>
I would however be fine with us having a more user friendly version scheme in<br>
addition to our current numbering.<br>
<br></blockquote><div><br><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Good. So maybe syncing could be kept for user-visible "large" version number plus maybe a
release date. Like "Calligra 3, December 2016 release" is just accurate enough for
infrequent releases. <br><br></div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
best regards<br>
Camilla<br>
_______________________________________________<br>
calligra-devel mailing list<br>
<a href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/calligra-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">regards, Jaroslaw Staniek<br><br>KDE:<br>: A world-wide network of software engineers, artists, writers, translators<br>: and facilitators committed to Free Software development - <a href="http://kde.org" target="_blank">http://kde.org</a><br>Calligra Suite:<br>: A graphic art and office suite - <a href="http://calligra.org" target="_blank">http://calligra.org</a><br>Kexi:<br>: A visual database apps builder - <a href="http://calligra.org/kexi" target="_blank">http://calligra.org/kexi</a><br>Qt Certified Specialist:<br>: <a href="http://www.linkedin.com/in/jstaniek" target="_blank">http://www.linkedin.com/in/jstaniek</a></div>
</div></div>