From kde-panel-devel  Mon Jun 30 18:04:54 2014
From: Aleix Pol <aleixpol () kde ! org>
Date: Mon, 30 Jun 2014 18:04:54 +0000
To: kde-panel-devel
Subject: Re: 5.0 and 5.1 Release Plans
Message-Id: <CACcA1Roe1f6GXGpYs9VEE4bAKhDRLLMYCCZZzHiK00ToG9ZhbA () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=140415152510976
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============6979819620787158141=="

--===============6979819620787158141==
Content-Type: multipart/alternative; boundary=047d7bdc16bc41ec3004fd1180f0

--047d7bdc16bc41ec3004fd1180f0
Content-Type: text/plain; charset=UTF-8

n Mon, Jun 30, 2014 at 7:55 PM, Marco Martin <notmart@gmail.com> wrote:

> On Monday 30 June 2014, Aleix Pol wrote:
> >
> > It's quite unfortunate the fact that we'll have a more schedule for the
> > frameworks and then the workspaces won't be able to take advantage of
> > those.
> >
> > I don't think it makes sense to decide to stop the development on a
> > plasma-framework, because after-all plasma depends on many other
> frameworks
> > just as well. It's random to choose Plasma just because it shares
> > maintainership.
> >
> > Aleix
> That's actually a good point..
> another option would be having 2 months releases for what depends from
> frameworks and put as dependency the second to last framework release, not
> the
> bleeding edge.
>
> in any case this idea as the 3 months makes abit more painful maintaining
> the
> devel environment with kdesrc-build


Well, in kdesrc-build I guess we just want to follow the master branch in
frameworks, we just won't be able to use the new API's there.

Aleix

--047d7bdc16bc41ec3004fd1180f0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">n Mo=
n, Jun 30, 2014 at 7:55 PM, Marco Martin <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:notmart@gmail.com" target=3D"_blank">notmart@gmail.com</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"">On Monday 30 June 2014, Aleix Pol wrote:<b=
r>


&gt;<br>
&gt; It&#39;s quite unfortunate the fact that we&#39;ll have a more schedul=
e for the<br>
&gt; frameworks and then the workspaces won&#39;t be able to take advantage=
 of<br>
&gt; those.<br>
&gt;<br>
&gt; I don&#39;t think it makes sense to decide to stop the development on =
a<br>
&gt; plasma-framework, because after-all plasma depends on many other frame=
works<br>
&gt; just as well. It&#39;s random to choose Plasma just because it shares<=
br>
&gt; maintainership.<br>
&gt;<br>
&gt; Aleix<br>
</div>That&#39;s actually a good point..<br>
another option would be having 2 months releases for what depends from<br>
frameworks and put as dependency the second to last framework release, not =
the<br>
bleeding edge.<br>
<br>
in any case this idea as the 3 months makes abit more painful maintaining t=
he<br>
devel environment with kdesrc-build</blockquote><div><br></div><div>Well, i=
n kdesrc-build I guess we just want to follow the master branch in framewor=
ks, we just won&#39;t be able to use the new API&#39;s there.</div><div>

<br></div><div>Aleix=C2=A0</div></div><br></div></div>

--047d7bdc16bc41ec3004fd1180f0--

--===============6979819620787158141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============6979819620787158141==--