Sorry I forgot,<br><br>I don't have access to my computer this weekend but will do that on Monday.<br>Regards,<br>Carl<br>-------- Original Message --------<br>On Mar 12, 2022, 12:52, Albert Astals Cid < aacid@kde.org> wrote:<blockquote class="protonmail_quote"><br><p dir="ltr">El dijous, 17 de febrer de 2022, a les 23:17:56 (CET), Carl Schwan va escriure:<br>
> Le jeudi 17 février 2022 à 11:09 PM, Albert Astals Cid <aacid@kde.org> a écrit :<br>
><br>
> > El dijous, 17 de febrer de 2022, a les 21:16:30 (CET), Carl Schwan va escriure:<br>
> ><br>
> > > Hi :)<br>
> > > Could we get Kalendar inside KDE Gear? Kalendar is mostly stabilized<br>
> > > and need a fast release cycle anymore.<br>
> ><br>
> > I am guessing you forgot a "doesn't" before that "need a fast", right?<br>
><br>
> yeah :)<br>
><br>
> > > More importantly, having our<br>
> > > release in sync with KDE PIM will help a lot in making sure that<br>
> > > a KDE PIM minor release won't break Kalendar silently and this would<br>
> > > also, allow us to move the new reminder service to Akonadi-calendar<br>
> > > and to share it with KOrganizer.<br>
> > ><br>
> > > See <a href="https://mail.kde.org/pipermail/kde-pim/2022-February/048374.html">https://mail.kde.org/pipermail/kde-pim/2022-February/048374.html</a><br>
> ><br>
> > What's the plan for automatically increaseasing version numbers if it it's released with KDE Gear?<br>
><br>
> We would simply follow the normal gear naming scheme: YY.MM.minor-release<br>
> since this is probably the simplest.</p>
<p dir="ltr">You have forgotten to deliver that change.</p>
<p dir="ltr">Branch 22.04 still identifies itself as 1.0.0</p>
<p dir="ltr">Albert</p>
<p dir="ltr">><br>
> > Cheers,<br>
> ><br>
> > Albert<br>
> ><br>
> > > Cheers,<br>
> > ><br>
> > > Carl<br>
><br><br><br></p>
</div>