summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20120527/3ce93a66
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20120527/3ce93a66')
-rw-r--r--zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment-0001.html22
-rw-r--r--zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment.html22
2 files changed, 44 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment-0001.html
new file mode 100644
index 000000000..55a80eb8c
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment-0001.html
@@ -0,0 +1,22 @@
+<p>Le 27 mai 2012 04:33, &quot;Franklin Weng&quot; &lt;<a href="mailto:franklin@goodhorse.idv.tw">franklin@goodhorse.idv.tw</a>&gt; a écrit :<br>
+[...]</p>
+<p>&gt;   Now my question is that, will the KDE update policy in<br>
+&gt; backports be still the same as before?<br>
+&gt;<br>
+&gt; I remember that when discussing if Mageia 1 would have KDE 4.7 in<br>
+&gt; backports, the answer was no because that kdepim was too unstable.</p>
+<p>It was part of the problem &amp; used to show that it was not that easy to do it.</p>
+<p>[...]</p>
+<p>&gt; For Mageia 2, again I&#39;d like to ask, if we will have KDE 4.9 in<br>
+&gt; backports after it releases in August?<br>
+&gt;<br>
+&gt; (Yes, I know that I can upgrade my KDE using cauldron.  But no, I<br>
+&gt; don&#39;t consider to upgrade my box with cauldron... it is far too<br>
+&gt; unstable than any version of kdepim.)</p>
+<p>So here we&#39;ve got some problems:<br>
+- Backports are not functional.<br>
+- Kde is still too big for a backport especially regarding our current (draft) backport policy where it should be validated by our QA. Not to mention that we&#39;ll have to update/backport somes dependencies to allow this.<br>
+
+- I personally won&#39;t push it to backport.</p>
+<p>Regards,<br>
+</p>
diff --git a/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment.html b/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment.html
new file mode 100644
index 000000000..55a80eb8c
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment.html
@@ -0,0 +1,22 @@
+<p>Le 27 mai 2012 04:33, &quot;Franklin Weng&quot; &lt;<a href="mailto:franklin@goodhorse.idv.tw">franklin@goodhorse.idv.tw</a>&gt; a écrit :<br>
+[...]</p>
+<p>&gt;   Now my question is that, will the KDE update policy in<br>
+&gt; backports be still the same as before?<br>
+&gt;<br>
+&gt; I remember that when discussing if Mageia 1 would have KDE 4.7 in<br>
+&gt; backports, the answer was no because that kdepim was too unstable.</p>
+<p>It was part of the problem &amp; used to show that it was not that easy to do it.</p>
+<p>[...]</p>
+<p>&gt; For Mageia 2, again I&#39;d like to ask, if we will have KDE 4.9 in<br>
+&gt; backports after it releases in August?<br>
+&gt;<br>
+&gt; (Yes, I know that I can upgrade my KDE using cauldron.  But no, I<br>
+&gt; don&#39;t consider to upgrade my box with cauldron... it is far too<br>
+&gt; unstable than any version of kdepim.)</p>
+<p>So here we&#39;ve got some problems:<br>
+- Backports are not functional.<br>
+- Kde is still too big for a backport especially regarding our current (draft) backport policy where it should be validated by our QA. Not to mention that we&#39;ll have to update/backport somes dependencies to allow this.<br>
+
+- I personally won&#39;t push it to backport.</p>
+<p>Regards,<br>
+</p>