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

List:       kde-release-team
Subject:    Re: Adding Kalendar to the KDE Gear release cycle
From:       Carl Schwan <carl () carlschwan ! eu>
Date:       2022-03-12 11:54:30
Message-ID: bl_Dvk2e1IKAnz9xMfnJ3dUflVsmcTis1cxLS-4UM2PiCfdDrLAtqwuihZkn4tLf-8sPOeXhaWLVtKto1X2TAh13xX14dI298omQ8yyvsuQ= () carlschwan ! eu
[Download RAW message or body]

[Attachment #2 (text/plain)]

Sorry I forgot,

I don't have access to my computer this weekend but will do that on Monday.
Regards,
Carl
-------- Original Message --------
On Mar 12, 2022, 12:52, Albert Astals Cid wrote:

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

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> &gt; Le jeudi 17 f&#233;vrier 2022 \
&#224; 11:09 PM, Albert Astals Cid &lt;aacid@kde.org&gt; a &#233;crit :<br> &gt;<br>
&gt; &gt; El dijous, 17 de febrer de 2022, a les 21:16:30 (CET), Carl Schwan va \
escriure:<br> &gt; &gt;<br>
&gt; &gt; &gt; Hi :)<br>
&gt; &gt; &gt; Could we get Kalendar inside KDE Gear? Kalendar is mostly \
stabilized<br> &gt; &gt; &gt; and need a fast release cycle anymore.<br>
&gt; &gt;<br>
&gt; &gt; I am guessing you forgot a "doesn't" before that "need a fast", right?<br>
&gt;<br>
&gt; yeah :)<br>
&gt;<br>
&gt; &gt; &gt; More importantly, having our<br>
&gt; &gt; &gt; release in sync with KDE PIM will help a lot in making sure that<br>
&gt; &gt; &gt; a KDE PIM minor release won't break Kalendar silently and this \
would<br> &gt; &gt; &gt; also, allow us to move the new reminder service to \
Akonadi-calendar<br> &gt; &gt; &gt; and to share it with KOrganizer.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; 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>
 &gt; &gt;<br>
&gt; &gt; What's the plan for automatically increaseasing version numbers if it it's \
released with KDE Gear?<br> &gt;<br>
&gt; We would simply follow the normal gear naming scheme: YY.MM.minor-release<br>
&gt; 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">&gt;<br>
&gt; &gt; Cheers,<br>
&gt; &gt;<br>
&gt; &gt; Albert<br>
&gt; &gt;<br>
&gt; &gt; &gt; Cheers,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Carl<br>
&gt;<br><br><br></p>
</div>



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