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

List:       kde-panel-devel
Subject:    Re: Proposal regarding plasmate's release
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2015-04-03 16:08:52
Message-ID: CAGeFrHBGwDNR2hG1=uiriCeBwF-PaZ38EoOvuRC5mN52s_N-VA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Apr 3, 2015 at 5:53 PM, Antonis Tsiapaliokas <
antonis.tsiapaliokas@kde.org> wrote:

> On Wed, Apr 01, 2015 at 01:51:02PM +0200, Marco Martin wrote:
> > Any news on this?
> > besides plasmate, the repository has other utilities (plasmoidviewer,
> > plasmaengineexplorer, plasmathemeexplorer, cuttlefish) that really NEED
> to be
> > released
>
> Yes, I am sorry for the delay.
>
> So lets summarize a bit.
>
> > On Thursday 29 January 2015, Giorgos Tsiapaliokas wrote:
> > > 1. move the plasmate repo away from extragear
>
> As it has been mentioned in previous email, we must first mail the
> kde-core-devel.
> As a new name i suggess the plasma-sdk and it will be under the
> kde/workspace.
>

Can it go under kde/workspace if in future it will depend on something in
extragear?

I still support doing the rest, and making / release.. I'm just not sure we
can do the move and release it with plasma.


>
> > > 2. release the plasmate repo together with plasma and all the
> applications
> > >      in it will follow plasma's version number. So there won't be
> > > plasmoidviewer 2.0
> > >      but plasmoidviewer 5.x
>
> So i will prepare a patch which will change the versions of
> plasmoidviewer, plasmaengineexplorer, plasmathemeexplorer, cuttlefish and
> plasmate.
> The version will be the same as Plasma's(5.2.90).
> And this repo will be released together with the Plasma's repo.


>
> > > 3. merge the frameworks branch into master and delete the frameworks
> branch
>
> So as it has been suggested we should tag the master branch, and after
> that we should merge
> the frameworks into the master, and delete the frameworks.
>
> Also in the previous mails, we said that we should the merge(frameworks
> into master)
> and then rename the repo in order to avoid changing the metadata twice.
>
> > > 4. make the PLASMATE_BUILD_WITH_KDEVPLATFORM off(false) by default and
> > > add a
> > >      message that will inform the user that the plasmate application
> > > isn't ready yet
> > >      for production.
>
> I will create a patch for this one too.
>
> So any objections/suggestions?
>
--
> Antonis Tsiapaliokas
>
> kokeroulis.gr
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr \
3, 2015 at 5:53 PM, Antonis Tsiapaliokas <span dir="ltr">&lt;<a \
href="mailto:antonis.tsiapaliokas@kde.org" \
target="_blank">antonis.tsiapaliokas@kde.org</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On Wed, Apr 01, 2015 at 01:51:02PM +0200, \
Marco Martin wrote:<br> &gt; Any news on this?<br>
&gt; besides plasmate, the repository has other utilities (plasmoidviewer,<br>
&gt; plasmaengineexplorer, plasmathemeexplorer, cuttlefish) that really NEED to \
be<br> &gt; released<br>
<br>
</span>Yes, I am sorry for the delay.<br>
<br>
So lets summarize a bit.<br>
<span class=""><br>
&gt; On Thursday 29 January 2015, Giorgos Tsiapaliokas wrote:<br>
</span><span class="">&gt; &gt; 1. move the plasmate repo away from extragear<br>
<br>
</span>As it has been mentioned in previous email, we must first mail the \
kde-core-devel.<br> As a new name i suggess the plasma-sdk and it will be under the \
kde/workspace.<br></blockquote><div><br></div><div>Can it go under kde/workspace if \
in future it will depend on something in extragear?</div><div><br></div><div>I still \
support doing the rest, and making / release.. I&#39;m just not sure we can do the \
move and release it with plasma.</div><div>  </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <span \
class=""><br> &gt; &gt; 2. release the plasmate repo together with plasma and all the \
applications<br> &gt; &gt;         in it will follow plasma&#39;s version number. So \
there won&#39;t be<br> &gt; &gt; plasmoidviewer 2.0<br>
&gt; &gt;         but plasmoidviewer 5.x<br>
<br>
</span>So i will prepare a patch which will change the versions of<br>
plasmoidviewer, plasmaengineexplorer, plasmathemeexplorer, cuttlefish and \
plasmate.<br> The version will be the same as Plasma&#39;s(5.2.90).<br>
And this repo will be released together with the Plasma&#39;s \
repo.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <span class=""><br>
<br>
&gt; &gt; 3. merge the frameworks branch into master and delete the frameworks \
branch<br> <br>
</span>So as it has been suggested we should tag the master branch, and after that we \
should merge<br> the frameworks into the master, and delete the frameworks.<br>
<br>
Also in the previous mails, we said that we should the merge(frameworks into \
master)<br> and then rename the repo in order to avoid changing the metadata \
twice.<br> <span class=""><br>
&gt; &gt; 4. make the PLASMATE_BUILD_WITH_KDEVPLATFORM off(false) by default and<br>
&gt; &gt; add a<br>
&gt; &gt;         message that will inform the user that the plasmate application<br>
&gt; &gt; isn&#39;t ready yet<br>
&gt; &gt;         for production.<br>
<br>
</span>I will create a patch for this one too.<br>
<br>
So any objections/suggestions?  <br></blockquote><blockquote class="gmail_quote" \
                style="margin:0 0 0 .8ex;border-left:1px #ccc \
                solid;padding-left:1ex">
--<br>
Antonis Tsiapaliokas<br>
<br>
<a href="http://kokeroulis.gr" target="_blank">kokeroulis.gr</a><br>
<div class="HOEnZb"><div \
class="h5">_______________________________________________<br> Plasma-devel mailing \
list<br> <a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div><br></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
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] 

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