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

List:       kde-panel-devel
Subject:    Re: 5.0 and 5.1 Release Plans
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2014-06-30 18:04:54
Message-ID: CACcA1Roe1f6GXGpYs9VEE4bAKhDRLLMYCCZZzHiK00ToG9ZhbA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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

[Attachment #5 (text/html)]

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

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


&gt;<br>
&gt; It&#39;s quite unfortunate the fact that we&#39;ll have a more schedule 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 frameworks<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 the<br>
devel environment with kdesrc-build</blockquote><div><br></div><div>Well, in \
kdesrc-build I guess we just want to follow the master branch in frameworks, we just \
won&#39;t be able to use the new API&#39;s there.</div><div>

<br></div><div>Aleix  </div></div><br></div></div>



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


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