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

List:       kexi-devel
Subject:    Re: Kexi 3.0 release is coming
From:       Jaroslaw Staniek <staniek () kde ! org>
Date:       2016-10-03 16:05:02
Message-ID: CAOj7QQ1a=m4gET6Wp=J2rt_tHpHW_ARnAzqnWf+xem33dxCwVw () mail ! gmail ! com
[Download RAW message or body]

On 3 October 2016 at 12:21, Luigi Toscano <luigi.toscano@tiscali.it> wrote:

> On Monday, 3 October 2016 12:14:21 CEST Jaroslaw Staniek wrote:
> > On 3 October 2016 at 12:06, Luigi Toscano <luigi.toscano@tiscali.it>
> wrote:
> > > On Monday, 3 October 2016 12:02:14 CEST Jaroslaw Staniek wrote:
> > > > Hi,
> > > > We're close to the 3.0 release. I plan to create tarballs today.
> > > >
> > > > Maintenance 3.0 branches have been created for Kexi projects
> > > > (kexi/kdb/kproperty/kreport git) already.
> > >
> > > We should finalize the move of the libraries outside of playground
> (which
> > > requires anyway passing through kdereview). We don't usually track
> stable
> > > branches of translations for playground modules (if it has releases,
> it's
> > > not
> > > playground).
> >
> > ​Good,
> > ​I remember I had a review like this when we had some time to discuss:
> > https://phabricator.kde.org/D2659.
> > I see no points against the move, just you may remember we were not
> really
> > sure the move is good idea at the moment or needed:
> > https://phabricator.kde.org/D2659#49459
>
> I did not wrote that the move is not needed. I was commenting about the
> final
> destination.
> If we put aside the destination, moving is required as "playground" and
> "stable branches" don't mix according our rules.
>
> The step about "moving to kdereview" is not new and it is the usual rule
> that
> should (have) happen(ed) like in other similar cases, again regardless of
> the
> destination.
>
> > Would you (or anyone else) be able to assist me in the move so we're
> ready
> > for the release as planned? I did not allocate any resources for exactly
> > this task today...
>
> You can release for the current, but we can't create the translation
> branches
> for the stable branch until this is settled. So if you want to release, I
> would say (but I'm not part of release-team, which is not in CC either),
> release today but then allocate the time to move stuff around.
>
>

Thanks Luigi
​OK with doing that later then.​
​
Could you look at to tell me what parts of https://phabricator.kde.org/D2916
are OK and what not yet? Probably especially the stable_kf5=3.0 values.

If there's anything documented feel free to share a checklist for the
'kdereview' task.


>
>
>


-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek

[Attachment #3 (text/html)]

<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 October 2016 at 12:21, Luigi \
Toscano <span dir="ltr">&lt;<a href="mailto:luigi.toscano@tiscali.it" \
target="_blank">luigi.toscano@tiscali.it</a>&gt;</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>On Monday, 3 October 2016 12:14:21 CEST \
Jaroslaw Staniek wrote:<br> &gt; On 3 October 2016 at 12:06, Luigi Toscano &lt;<a \
href="mailto:luigi.toscano@tiscali.it" \
target="_blank">luigi.toscano@tiscali.it</a>&gt; wrote:<br> &gt; &gt; On Monday, 3 \
October 2016 12:02:14 CEST Jaroslaw Staniek wrote:<br> &gt; &gt; &gt; Hi,<br>
&gt; &gt; &gt; We&#39;re close to the 3.0 release. I plan to create tarballs \
today.<br> &gt; &gt; &gt;<br>
&gt; &gt; &gt; Maintenance 3.0 branches have been created for Kexi projects<br>
&gt; &gt; &gt; (kexi/kdb/kproperty/kreport git) already.<br>
&gt; &gt;<br>
&gt; &gt; We should finalize the move of the libraries outside of playground \
(which<br> &gt; &gt; requires anyway passing through kdereview). We don&#39;t usually \
track stable<br> &gt; &gt; branches of translations for playground modules (if it has \
releases, it&#39;s<br> &gt; &gt; not<br>
&gt; &gt; playground).<br>
&gt;<br>
&gt; ​Good,<br>
&gt; ​I remember I had a review like this when we had some time to discuss:<br>
&gt; <a href="https://phabricator.kde.org/D2659" rel="noreferrer" \
target="_blank">https://phabricator.kde.org/D2<wbr>659</a>.<br> &gt; I see no points \
against the move, just you may remember we were not really<br> &gt; sure the move is \
good idea at the moment or needed:<br> &gt; <a \
href="https://phabricator.kde.org/D2659#49459" rel="noreferrer" \
target="_blank">https://phabricator.kde.org/D2<wbr>659#49459</a><br> <br>
</span>I did not wrote that the move is not needed. I was commenting about the \
final<br> destination.<br>
If we put aside the destination, moving is required as &quot;playground&quot; and<br>
&quot;stable branches&quot; don&#39;t mix according our rules.<br>
<br>
The step about &quot;moving to kdereview&quot; is not new and it is the usual rule \
that<br> should (have) happen(ed) like in other similar cases, again regardless of \
the<br> destination.<br>
<span><br>
&gt; Would you (or anyone else) be able to assist me in the move so we&#39;re \
ready<br> &gt; for the release as planned? I did not allocate any resources for \
exactly<br> &gt; this task today...<br>
<br>
</span>You can release for the current, but we can&#39;t create the translation \
branches<br> for the stable branch until this is settled. So if you want to release, \
I<br> would say (but I&#39;m not part of release-team, which is not in CC \
either),<br> release today but then allocate the time to move stuff around.<br>
<span class="gmail-m_-2270468861568326371HOEnZb"><font \
color="#888888"><br></font></span></blockquote><div><br><div \
style="font-family:monospace,monospace;font-size:small;display:inline" \
class="gmail_default"><br>Thanks Luigi<br>​OK with doing that later \
then.​</div><div style="font-family:monospace,monospace;font-size:small;display:inline" \
class="gmail_default">​ <br>Could you look at to tell me what parts of <a \
href="https://phabricator.kde.org/D2916">https://phabricator.kde.org/D2916</a> are OK \
and what not yet? Probably especially the stable_kf5=3.0 values.<br><br></div><div \
style="font-family:monospace,monospace;font-size:small;display:inline" \
class="gmail_default">If there&#39;s anything documented feel free to share a \
checklist for the &#39;kdereview&#39; task.<br></div><div \
style="font-family:monospace,monospace;font-size:small;display:inline" \
class="gmail_default"><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"><span \
class="gmail-m_-2270468861568326371HOEnZb"><font color="#888888"><br> <br>
<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><div \
class="gmail-m_-2270468861568326371gmail_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/<wbr>jstaniek</a></div> </div></div>



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

Configure | About | News | Add a list | Sponsored by KoreLogic